Re: RI - pros and cons

I would like to say I agree with something you said: But I can't. I think you totally misunderstand the prpose of RI.

Any database, other than one sitting in a read-only tablespace without RI, is one I will refuse to work on ... except to fix it.

Daniel Morgan

Don Smy wrote:

> A major drawback of using RI is that it tends to make your application
> database vendor specific. If you intend building apps that will be used by
> different brands of databases I'd say putting the RI in your app is a good
> thing.
>
> Another reason for not using RI is that RI is designed to stop people who
> aren't experts from doing stupid things. Quite often there are very good
> reasons for circumventing RI in the application (particularly during data
> conversion projects or providing data importing facilities). For conversions
> I guess you could just drop the constraints, do the conversion and then put
> them back on. For importing it may not be that easy.
>
> If none of these issues apply to your environment then I think your DBA just
> doesn't like work....
Received on Fri Mar 22 2002 - 11:40:36 CST