# FRQ: Database Inheritance

**URL:** <https://community.fibery.io/t/frq-database-inheritance/4528>\
**Category:** Ideas & Features\
**Created:** [June 1, 2023, 4:44am UTC](https://community.fibery.io/t/frq-database-inheritance/4528 "2023-06-01T04:44:42Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [June 3, 2023, 6:04pm UTC](https://community.fibery.io/t/frq-database-inheritance/4528/5 "2023-06-03T18:04:34Z")

</div>

I still think the Lookup-based approach is potentially non-ideal and quite limited (even if editing in looked-up entity is added) vs. some kind of “inheritance” system or at least [Individual Layouts for a node, hide fields etc](https://community.fibery.io/t/individual-layouts-for-a-node-hide-fields-etc/995) and/or [Tab Views in Entity Pages](https://community.fibery.io/t/tab-views-in-entity-pages/2931). The newer ability to Hide and Collapse Fields and Relations is helpful to deal with field proliferation but doesn’t address the need for different views of same/related data based on context.

---

_[View the full topic](https://community.fibery.io/t/frq-database-inheritance/4528)._