Database more than 70 table design of some thinking ...

Some thoughts on the design of the database of more than one table ...

Yesterday at a seminar, a comrade said he for a university in Gansu province to do a construction department of the management of the website with a full number of tables, I heard a surprise, casually to sentence, this dude pull it!

I think that the individual departments of the school, no matter how complex, so many tables are not conducive to real system development, and the individual departments can not be so complex business. So stand on this guy's point of view, the reason is only one, he split the table is very meticulous, a single table field is very small, the function is very single.

It seems to be understandable, but with more than one table, I have hardly seen a few of these huge projects for many years. Always feel strange, so I always want to theoretically analyze his design is reasonable. Database design I believe most developers know to abide by the design paradigm, this part of the content can refer to my previous paradigm article, so I can start from the paradigm, do an analysis? The question came, and I was somewhat puzzled, and the following conclusions were drawn:

Paradigm as the theoretical basis of database design, in fact, is not perfect, some cases are not suitable for practical development. The guiding principle of the paradigm is to be as clear, simple and clear as possible, and to simplify the complex relationship. But the problem comes out, the actual development to consider efficient, simple, as far as possible to avoid multi-table query. And this principle is exactly in conflict with the paradigm theory, so how to do it? I think everyone will have a different approach, of course, the most important thing is the accumulation of their own work experience, and the actual business understanding, to design a truly suitable for their own database structure.

This is a tall man's saying:

The so-called paradigm refers to the design of efficient and convenient extension of the database guidelines, but the actual is only as a reference , because in accordance with the standard design paradigm, query is very complex, inefficient, not necessarily suitable for practical development. In the actual work, there is only one principle for the actual database design: " reduce the number of table queries as much as possible in the business ".

Finally, for the brother of more than one table, can only be said to conform to the simplification of the paradigm, but the actual number of tables in the multi-table joint query for developers is not a goodidea.

Welcome to discuss with us ...

Database more than 70 table design of some thinking ...