Re: Table acting as a relation table
From: Guy <guhar1_at_yahoo.com>
Date: 11 Apr 2007 11:59:50 -0700
Message-ID: <1176317990.500750.105560_at_d57g2000hsg.googlegroups.com>
Date: 11 Apr 2007 11:59:50 -0700
Message-ID: <1176317990.500750.105560_at_d57g2000hsg.googlegroups.com>
On Apr 11, 1:07 pm, Lennart <erik.lennart.jons..._at_gmail.com> wrote:
> Guy wrote:
> > So all I have to do is to consider [HOSP_CODE, CLINIC_CODE] as my
> > primary key.
> > The model is valid, each record have a unike key, and my relations are
> > expressed properly.
> > Thanks.
>
> Why [HOSP_CODE, CLINIC_CODE] as primary key?
>
> /Lennar
A clinic code can only be linked to one and only one hospital. I could enforce this by code, but it is customary in my company to create a primary key to enforce this, and it helps the QA and support understand the validity rules of a table. Received on Wed Apr 11 2007 - 20:59:50 CEST