Re: Must we also create separate tables?
Date: Mon, 27 Oct 2008 19:14:11 GMT
Message-ID: <7qoNk.755$225.147_at_nwrddc02.gnilink.net>
"paul c" <toledobythesea_at_oohay.ac> wrote in message
news:_ElNk.4298$%%2.1321_at_edtnps82...
> Srubys_at_gmail.com wrote:
> ...
>>
>> Say we have non-normalized table STUDENT:
>>
>> STUDENT ( STUDENT#, STUDENT_NAME, SUBJECT1#, SUBJECT2#, SUBJECT1_NAME,
>> SUBJECT2_NAME, TEACHER1_NAME, TEACHER2_NAME )
>>
>>
>> I realize best thing to do would be to create two tables:
>>
>> STUDENT-SUBJECT ( STUDENT#, SUBJECT#, SUBJECT_NAME, TEACHER_NAME )
>>
>> STUDENT ( STUDENT#, STUDENT_NAME)
>>
> ...
>
>
> Heh, just to muddy the waters a little or even a lot, the conventional
> normalization discipline is really just a way to help determine a simple
> structure that avoids a lot of constraint verbiage. From what I gather of
> the typical SQL product it is effectively a sop that allows them to
> cop-out and not give very full constraint support.
>
Nah! Received on Mon Oct 27 2008 - 20:14:11 CET