X Close Editor

Submitted by: Will

Title

Comment
To be fair not many DBMSs supported declarative foreign key constraints before the 90s - but some did support triggers before then. So it might be expected that older systems may not have foreign key constraints in place. If this is the case then I would say implementing the constraints in triggers (rather than in application code) was the right thing to do at the time. However it would make sense today to replace the trigger implementation of the foreign key constraints with declarative constraints. That being said, the support for declarative constraints in SQL is still far from adequate and you still have to do far more in triggers than would be ideal.

Cancel Delete Delete & Ban

Updating Comments page...

X Close Editor

Submitted by: Anonymous

Title

Comment
Some kind of people usually don't like relation ship. Relation ship is not good as you think. example. if you querry db with a db have many many relation ship table. it will be slow down. but when insert or update, it really faster and easy mantain. So, according your goal. design your db correct. this is my idea

Cancel Delete Delete & Ban

Updating Comments page...

X Close Editor

Submitted by: Anonymous

Title

Comment
Yes, that's how unexperienced designers misunderstand the built in powers of the DB. Crazy story though; I wonder what made them do that...

Cancel Delete Delete & Ban

Updating Comments page...