Re: To foreign key or not to foreign key

FK constraint is good to have for data consistancy BUT you don't need index for all of columns if the parent table is not updated or a simple lookup table is parent key, otherwise having an index on FK columns will protect you from locking on that columns.

Thanks,

On Tue, 14 Dec 2004 08:33:52 -0800 (PST), Fuad Arshad <fuadar_at_yahoo.com> wrote:
> I know this has been discussed here before and i did find a couple of jonathan lewis's old posts
>
> The thing is we have a project where the consultants want to ensure about 10-15 foreign keys per tables to enforce parent child relationships.
> I've seen locking issues beforer and was wondering if the list could put down a some pros and cons as to going or not going with a primary foriegn key strategy.
> This is a oltp type system and sub second response is what the enpd product requires( isnt that the description of every project these days).
> The consultants want every foreign key indexed. which i think is way too much a performance degradation since inserts are going to be major part of the application.
>
> --
> http://www.freelists.org/webpage/oracle-l
>

--
http://www.freelists.org/webpage/oracle-l