RE: To foreign key or not to foreign key
- From: "Powell, Mark D" <mark.powell@xxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Tue, 14 Dec 2004 12:53:56 -0500
I find it highly questionable for normalized tables to have 10 - 15 foreign
keys to begin with.
HTH -- Mark D Powell --
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Fuad Arshad
Sent: Tuesday, December 14, 2004 11:34 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: To foreign key or not to foreign key
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.
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
