Generic vs. Granular entities (when to split DBs)

[njyo]

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

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…