Need help understanding a particular piece of drupal SQL tables?

Question

MySQL

Hello, there was a need to implement something like the types of materials from drupal, well, that is, sets of pages with different fields and their number, I have no idea how to do this, can someone tell me an approximate set of tables for storing pages and a variable number of fields (image field, text field, etc. ), how to make 1 page with the required number of fields is understandable, but how to create a page with this set every time is not (the types of materials are stored in separate tables). here is the drupal database schema as a sample www.drupal.ru/files/er_db_schema_drupal_7.png
well, for example, the user decided to create a set BUYING A CAR and decided that it would consist of 10 stages 1 stage is a page where there is only a field for attaching a photo of a car 2 stage is a description, that is, there is a page with a test field, and so on up to 10, with the number and type of fields on each page the user determines at the stage of creating a set, that is, the set can have at least 1000 stages, and each of the 1000 stages can have at least 1000 fields of a predetermined type that it can choose from the type list (image field, text field, bullfield). and each user who wants to use the previously defined set must receive exactly the number of stages and fields in them that was already defined in order for him to be able to fill in and save them, and not just once, because, as in the upper example, there can be many different machines

Answer 1

In my opinion, something very many powers are hung on the user. The user, of course, can go to the Drupal admin panel, create the necessary dictionaries and taxonomy terms, create the necessary web forms, create content types with the necessary fields.
One thing is not clear, why then do you need a developer?

Answer 2

Hello.
Your task, I think, simply boils down to making your own kind of form constructor for each page, only you display the field values.
Here you have, for example, a navigation page (main).
Navigation
ID | ParentId | title | description | URL | Order
Here you have, for example, a form constructor.
FieldTypes
Id | title | Alias
​​Values
​​- TextField
- TextArea
- TypeMCE
- Select
- Image
- File
FieldGroup
Id | title | NavigationId (page link)
FieldsAndGroups
Id | FieldTypeId (link to FieldTypes) | FieldGroupId (association with FieldGroup) | value | Order
Something like this)