RE: Design question.

[Mercadante, Thomas F]

Title: RE: Design question.

I agree that "Not Good" might characterize this - what it points out is "not good" table design.  the parent table now will have a row with two unique items - the existing primary kay, and a combination of two other columns.

 

I would review the tabl3e design and decide if something else needs to be done.

 

Tom Mercadante
Oracle Certified Professional

-----Original Message-----
From: Whittle Jerome Contr NCI [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 31, 2002 12:07 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Design question.

Chris,

Is there a unique constraint based on the two fields in the parent table? If so it might work OK. Still there are the problems of referential integrity, orphan records, etc. If there isn't a unique constraint in the parent table, you can also add in potential many-to-many relationships as a problem to.

Basically I'd say this falls into the "Not Good" category.

Jerry Whittle
ACIFICS DBA
NCI Information Systems Inc.
[EMAIL PROTECTED]
618-622-4145

-----Original Message-----
From:   Grabowy, Chris [SMTP:[EMAIL PROTECTED]]
Sent:   Friday, May 31, 2002 10:33 AM
To:     Multiple recipients of list ORACLE-L
Subject:        Design question.

We have a designer that is adding a FK on two columns from one table to
another.  These two columns are not in the parent table's primary key.

So we are kind of scratching our heads wondering if you can, from a proper
design point of view, create such a FK?  It appears that if you update one
of the two columns in the child table then you would need to create a new
record in the parent table. 

Thoughts??