I am interested to know the pros and cons of creating a custom system supported by a database similar to the one described below:
It supports 6 tables.
Essence: Let's say something “physical” that can exist and stores details against it (Hilton Hotel, Tony Taxi, One Bar)
Entity Type: Grouping / Object Type (Bar, Hotel, Restaurant)
Metadata: Any details describing or belonging to an element of an object (IR232PH, foo@bar.com , 555-555-555)
Metadata Type: Grouping / Metadata Type (Postal Code, Phone, Email, Address)
Entity Relationship: Ability to group any element of an object into another (Entity1-Entity2, Entity3)
Entity Relationship Type: Grouping / Entity Type Relationship .
I see how this model is good for entities that are similar, but do not always have the same number of attributes.
What are the advantages / disadvantages of using it, as for entities, as described?
- An artist can perform (type of relationship) at the venue.
- An artist can support (type of relationship) another artist
What would be the pros / cons of using it also for storing more standard objects such as system users?
- The user can have a favorite (type of relationship) place / artist / bar, etc.
- User can have a visit event (relationship type)
Could you please consider that it has news and blog posts?