On the paradigm of MySQL--the thinking of inverse paradigm

Database design, is a model, is in the actual production of the project, according to how the steps to do. Less redundancy, more than a pair of ah, and so on.

So back to the question: is the database meant to be added or to be queried? This problem has some axes, in order to increase the deletion of the four laws, it is important.

Then the database itself is used by people. So the streamlining of the database, through the paradigm of streamlining, for us, is the most important?

The database itself, is a kind of logical thinking of the storage, the existence of our understanding of a project, a data of the mind map-in short, is not the most important, but can be used.

When using MySQL, emphasis is placed on multi-table search and emphasis on reducing redundancy. But I think from the reality, the single-table joint search, appropriate redundancy, but will be more to improve the application of a project.

On the paradigm of MySQL--the thinking of inverse paradigm