Exactly. Get a design with three or four levels of PK/FK relationships and watch the cascading everytime a mistyped natural PK needs to be edited to the correct value. It's just not practical.
Cheers Nuno Souto [EMAIL PROTECTED] ----- Original Message ----- > > eg. if you update the natural key in the parent, you must also update the > natural > key everywhere it appears as an fk. > > This gets really ugly when you think about making modifications to the > schema. > -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Nuno Souto INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
