Specifying the tables that I am in doubt are, in my case, a company work for the college, the tables: Entry and Diagnosis, where the input is when someone brings some equipment, and then the diagnosis is made, but the diagnosis has more than 40 fields, so I've divided them into 5 tables by categories. I would like to ask if dividing a table into 5 because it contains too many fields in a single table, is it not following the normalization rules?
Database Modeling
1
asked by anonymous 25.05.2016 / 15:49
1 answer
2
This has nothing to do with normalization, neither for better nor for worse. Unless you have hidden requirements in the question. I can not talk about what is not written.
In general I would not do this separation unless you have a good reason. I see disadvantages, slows down, complicates the application, makes it easier to make more mistakes. The advantage of being "more organized" is quite questionable. Some will say that it is disorganizing, since to separate what is a thing only probably is something worse.
Every decision that a programmer must make is based on realistic justifications and well-defined criteria, bringing some real advantage without undesirable disadvantages. I doubt I can make a good case for separating these fields.
25.05.2016 / 16:08