|
Posted by --CELKO-- on 11/23/07 13:24
>> OK, I understand. Yes, you are right, the design of DB is not normalized correctly. But for some reasons we decided to do it this way. <<
Then go back and do it right. Would you accept an automobile mechanic
telling you that he did not put your tires on right, but as long as
you don't go too fast or turn too sharply, there will not be any
problems?
>> It is not that important to have the FK defined in the DB, the applications will ensure the integrity of the data. <<
How do you plan to hire only perfect programmers now and in the future
who will never subvert your intended business rules buy always writing
perfect application code? How do you plan on keeping people away from
QA and other tools that go directly to this disaster waiting to
happen?
Navigation:
[Reply to this message]
|