M
M
muratphpcss2018-09-28 11:47:12
Database design
muratphpcss, 2018-09-28 11:47:12

How to classify this scheme and what analogues are there?

Good afternoon!
There is such a database design scheme:
5bade8a1ad4d5584227823.png
The meaning of this scheme is to organize an entry point for all products of a company, this gives some flexibility.
That is, the following is done:
1) A list of tables is created in "tables" (where name is the name of the table in the database, pk_name is the name of the primary key of this table)
2) A list of products is created in "products" (where table_id is the table identifier from tables, pk_value - the value of the primary key of the table)
3) The tables some_product, another_product, etc. are created. which contain different fields for a specific product The
question is:
1. What are such schemes called?
For example, EAV is also designed for database flexibility, but in EAV, columns are stored as records in the database.
2. Therefore, I cannot understand whether it is advisable to compare this scheme with EAV?
3. What analogues are there to understand what is better to use?
Thank you very much in advance!

Answer the question

In order to leave comments, you need to log in

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question