database - Is it bad to use redundant relationships? -
Suppose my database has the following tables:
Now all my The queries depend on the company table
Edit 1: Background is a problem with the problem that is a problem with an intersection. See.
Editing 2: No company can change its company.
Editing 3: I do not write mysql questions. I use an abstract layer (Django).
This is bad behavior because updating your unnecessary data is independently and therefore unnecessarily. A process that is full of potential for error (even assigned to automatic cascading and to be maintained separately)
By starting this relationship, you effectively deprecate your database can do. Demilization is sometimes necessary for execution, but by your question it seems that you are simplifying your SQL.
Use other mechanisms to summarize the complexity of your database: View, stored process, UDF
Comments
Post a Comment