i dont disagree with u. even i dont like the below mentioned
implementations. i always prefer seperate tables. btw "lot of rows" is very
subjective.
i dont know what u mean by "I have to have a table that contains every
possible combination of SPLT and TYPE. ".
anyways, its a common practice to create surrogate keys to avoid composite
foreign keys. imagine a structure flowing from
master to detail with 20 sub levels one below other. ur last child table
would have a foreign key with ~20 columns.
-Mandar
-----Original Message-----
Sent: Friday, March 23, 2001 8:16 PM
To: Multiple recipients of list ORACLE-L
I hate to be picky, but I don't like either of the solutions proposed below.
For the first solution, that means that I would have to have the repeating
values 'SPLT' and 'TYPE' in every row of the DOCTOR table, which is a table
with a lot of rows in it.
For the second solution, I have to have a table that contains every possible
combination of SPLT and TYPE.
Both solutions seem to be wasteful and clumsy. Please don't take this as a
direct criticism of you, but I still don't see how a single code table can
be implemented well using FK relationships.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Mandar Ghosalkar
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
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).
