> -----Original Message-----
> From: Ryan Fox [mailto:[EMAIL PROTECTED]]
> Sent: 29 October 2001 00:55
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Data Normalization Paradox
>
>
> > Among other criteria, it mentions that in first order normalization
> > "No
> repeating groups of data are allowed". It then gives a table
> with 3 rows of data, and shows that one of the columns
> (company name) has the same entry in two of the rows. It
> says "this table is not in 1st normal form". For the correct
> way of doing it, it shows the same table, with that column
> changed to (company name id) and links it to another table
> that has two columns, company name id, and company id.
>
>
> Right. The main reasons for doing this are to minimize data
> storage space (the number '1' takes far less space to store
> than the string 'Foo Company'), ensure data integrity (make
> sure you don't have entries such as 'Foo Company' and 'foo
> company'), and to speed queries (matching integers can be
> performed by the sql server MUCH qiucker than matching strings).
>
> Hope this helps,
> Ryan Fox
I'd say that minimizing data storage isn't even a reason, just a mere
sideeffect.
Data normalisation ensures that whenever you want to change something
about the name of the company,
you only have to change the data in one place. It enforces data
integrity. It makes life a lot easier,
and queries (usually) faster.
As for scoring, you should have a table ( animation_id, judge_id, score
) or something - with animation_id and judge_id as primary key.
-S
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
