# Database internal relationship new view

**URL:** <https://community.fibery.io/t/database-internal-relationship-new-view/10141>\
**Category:** Ideas & Features\
**Tags:** views\
**Created:** [December 8, 2025, 9:37am UTC](https://community.fibery.io/t/database-internal-relationship-new-view/10141 "2025-12-08T09:37:57Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [December 8, 2025, 12:48pm UTC](https://community.fibery.io/t/database-internal-relationship-new-view/10141/4 "2025-12-08T12:48:30Z")

</div>

> [@SC\_Bryan](#):
>
> but it doesn’t exactly make it easy to work with, nor very readable

True! This would be a good use case for something like this: [Ultra Compact Board View to Solve Financial Forecasting / Single Field Table View / Pivot in Table View](https://community.fibery.io/t/ultra-compact-board-view-to-solve-financial-forecasting-single-field-table-view-pivot-in-table-view/10131)

> [@SC\_Bryan](#):
>
> Nevertheless I think the feature would still be nice and would give a very powerful visualization tool to any organization that has internal relationships in databases and wants some insight into them, be it dependencies, related-ness, duplicate-ness, or anything else really.

Yeah, I’m just thinking of maybe a way to make it more flexible and not just a single use case. How it could be set up in a way that it can also help with other situations.

---

_[View the full topic](https://community.fibery.io/t/database-internal-relationship-new-view/10141)._