# Generic vs. Granular entities (when to split DBs) **URL:** \ **Category:** Get Help\ **Created:** [February 20, 2024, 2:54pm UTC](https://community.fibery.io/t/generic-vs-granular-entities-when-to-split-dbs/5882 "2024-02-20T14:54:00Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\ **Post date:** [February 21, 2024, 4:01am UTC](https://community.fibery.io/t/generic-vs-granular-entities-when-to-split-dbs/5882/2 "2024-02-21T04:01:36Z")
Good question! We have not taken a purist approach to the dilemma and thus have a mix of granular entities (e.g. Task and Build Task, Client Org and Partner Org) but also some generic ones (Meeting, Person) with loads of partially relevant fields. I would really want to have inheritance across the entities, as that would allow for common fields with granular extensions: > [@FRQ: Database Inheritance](https://community.fibery.io/t/frq-database-inheritance/4528): > > Hi, For certain types of databases (i.e. Tasks, People, Organisations, Tools) I would like to have the ability to inherit/extend databases. For example: I want a base database called Person which has a few basic fields: given name, surname, email, phone, etc. I’ll have database called Staff that extends Person, which in addition has fields like: join date, role, salary, etc. I’ll have a database called Contact that extends Person, which adds fields like: company, meetings, etc. I’ll have a d… --- _[View the full topic](https://community.fibery.io/t/generic-vs-granular-entities-when-to-split-dbs/5882)._