Re: Table acting as a relation table
From: Guy <guhar1_at_yahoo.com>
Date: 10 Apr 2007 15:32:01 -0700
Message-ID: <1176244321.679105.207590_at_e65g2000hsc.googlegroups.com>
Date: 10 Apr 2007 15:32:01 -0700
Message-ID: <1176244321.679105.207590_at_e65g2000hsc.googlegroups.com>
I am going to rephrase my question:
T_HOSPITAL <-------------- T_HOSPITAL_CLINIC <-------------> T_CLINIC
With my asssociation table I can define which clinic belongs to which
hospital. Someone told me that such table cannot have the only two
field HOSP_CODE, CLINIC_CODE, but some other "key" field should be
there. Quote "a table with no key to identify each row should not be
modeled".
HOSP_CODE HOSP_CODE
CLINIC_CODE
CLINIC_CODE
Obviously my table will work as is. Is there however a rule I am enfringing ? Received on Wed Apr 11 2007 - 00:32:01 CEST