data integrity constraints: objects vs database
From: Scott Blankenship <scott.blankenship_at_relizon.com>
Date: 26 Sep 2001 07:41:04 -0700
Message-ID: <bfdcd9e6.0109260641.1c20d1fc_at_posting.google.com>
Date: 26 Sep 2001 07:41:04 -0700
Message-ID: <bfdcd9e6.0109260641.1c20d1fc_at_posting.google.com>
We're going through a major re-design. One of the debates that has
come up is on the subject of integrity constraints. We have a DBA that
doesn't like putting many (or any) integrity constraints in the
database. He says the applications, particularly with OO, should
prevent integrity problems and that the database will perform better
without them.
I say having the constraints in the database make more sense because
of manual data manipulation by the support groups, and because
sometimes programs (even OO programs) have bugs.
I'm just looking for some more opinions. What do you guys think?
Scott