Re: Design Question

From: Alan <not.me_at_uhuh.rcn.com>
Date: Sat, 16 Oct 2004 12:46:03 GMT
Message-ID: <fK8cd.302$UX3.182_at_trndny03>


It's should be one big table. One to one relationships are data modelling constructs. They almost always get merged into one actual table, and in this case, I don't see a reason not to. Some additional information may be helpful.

"Ray" <rgss_at_comcast.net> wrote in message news:nJXbd.370887$mD.195310_at_attbi_s02...
> Ok I've got a question on a database I am designing.
>
> Here is some tables I have.
>
> Contractors(contractorID,contractorsExtInfoID)
>
> ContractorsExtInfo
> (contractorsExtInfoID,contractorsLicenseInfoID,contractorsReferenceInfoID)
>
> ContractorsLicenseInfo(contractorsLicenseInfoID,...)
>
>
>
> ContractorsReferenceInfo(contractorsReferenceInfoID,...)
>
>
>
> Ok all these tables are gonna have one to one relationships
>
>
>
> I put a foreign key for the ContractorsExtInfo table in the Contractors
> table, then
>
> I put the rest of the foreign keys in ContractorsExtInfo, I did this
mostly
> to keep the contractors table neater and also for more flexibilty, but...
>
>
>
> Does this make any sense, and if it does then is doing it this way correct
> or even ok?
>
>
>
> I know I don't really need to but should I put a contractorID field in the
> other tables, so I can relate back to the Contractors table?
>
>
>
> Thanks Ray
>
>
>
>
Received on Sat Oct 16 2004 - 14:46:03 CEST

Original text of this message