There is a website template, after changing any field users available, data should be stored in the database. The number of fields that adds changes the user can change in the future.

How does such a database structure implement, how will the front be able to interact with a similar structure?

Should the front add similar fields making a request with the name through the Beck or is it regulated only by Beck?

Do you need to use in such cases not a relational base (due to its uncontrolled fields)?

"Should the front add similar fields making a request with an indication of the name through the behead or is it regulated only by Beck?" -The question is meaningless.

Ипатьев2021-08-27 21:57:07

"The number of fields that adds changes the user may change in the future." -This is a very bad idea that always ends very badly. If you are not in the blood enmue with those who will continue to accompany this site, then it is not worth doing it. However, if you are, it is also not worth

Ипатьев2021-08-27 21:57:07

It is possible that the wording is so-so, but this part of the question can be docked how "to give the ability to change the structure of the base directly from the front application, or it should be back"

S.H.2021-08-27 21:57:07

What does it mean "should be back"? At wishes, at 12 o'clock in the morning, randomly add two fields to database and delete five?

Ипатьев2021-08-27 21:57:07

@ S.H. Thanks for the specific wording. Approximately a similar problem and appeared. I know that violates many concepts of database management on the front side. But if the user allows you to change, create dozens of pages, how to collect them, and where to store them? The database will be available only to the user and no more than anyone. All his actions will break only his site

Locker2021-08-27 21:57:07