Re: data integrity constraints: objects vs database

you both are correct in your points. contraints in the database do significantly slow down performance. they also make databaes maintenance, such as imports and mass loading much more difficult, since in these cases constraints generally must be dropped and recreated. if one takes a cue from Oracle itself, note that oracle applications, such as Financials and Manufacturing, have few, if any, constraints in the database for the reasons stated by your DBA. if Oracle won't use them for their own applications, what does that tell you ?

"Scott Blankenship" <scott.blankenship_at_relizon.com> wrote in message news: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
Received on Fri Sep 28 2001 - 08:20:51 CEST