Answer the question
In order to leave comments, you need to log in
What to read about the database?
Are there any best practices for the database?
What is the best way to name tables, fields, in which cases it is better to use one-to-many or create a separate table for connectivity, in which cases it is better to make a normalized database, and in which it is better not to do this
In general, all sorts of different tips on building a database
Answer the question
In order to leave comments, you need to log in
There are no best practices for the database, alas.
Name tables and fields as God puts on your soul, sometimes use one to many, and sometimes create a separate table for connectivity, you can make a normalized database, or you can not.
In general, play along.
Are there any best practices for the database?Yes. When the structure of this is most consistent with the physical model and simplifications are not time bombs for the project. And the use of the methods you listed (and even then not completely) is only part of the architecture.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question