Re: Database Design Question - any suggestion?

From: <greatguangong_at_gmail.com>
Date: 10 Dec 2004 02:17:29 -0800
Message-ID: <1102673849.011489.221980_at_c13g2000cwb.googlegroups.com>


Normalization is the key.

On the surface, color and size are candidates for separate tables on their own, since they are entities with attributes. If you can see in advance that colors will never carry attributes on their own except white/blue/red/violet, then they will become attributes, i.e. another column.

But size is a different issue. Can easily spawn more attributes, e.g. size#, name (XXXL,XL,L,M,S,SS), region (European code, American code, etc).

Leaning towards previous study of vendor schemas, product name is usually part of the product table too. Though please bear in mind it is almost always useful to use your own primary key column, instead of like article#.

imagine in the future if a vendor comes along with similarly-named products...oops.

guangong
Oracle10g/9i/8i DBA (Linux Specialty) Received on Fri Dec 10 2004 - 11:17:29 CET

Original text of this message