J
JRough
This database outputs to Indesign for printing and needs to be
structured around what it does. The database worked until recently we
needed to add products of a different type from clothing. The product
number is the name of a product for a company for example some type of
clothing, a sweater.
Product
rodNum, size, price
Skew:skewNum, prodNum, color
This works great for clothing, sweaters, shirts where there are only
size attributes and color for the skew.
But for a company that advertises tennis shoes for example this
wouldn't work. There would be other attributes such as upper sole,
whatever.
So to normalize it I thought of
ProductrodID, prodNum
AttributesrodID, attribute
Skew:skewID, ProdID, skewNum, color
I am not sure this is it. It may need a parent child relationship in
product to attributes. Is there a way to get rid of the attributes
table and just have product and skew so it works also for the
clothing?
thanks,
structured around what it does. The database worked until recently we
needed to add products of a different type from clothing. The product
number is the name of a product for a company for example some type of
clothing, a sweater.
Product
rodNum, size, priceSkew:skewNum, prodNum, color
This works great for clothing, sweaters, shirts where there are only
size attributes and color for the skew.
But for a company that advertises tennis shoes for example this
wouldn't work. There would be other attributes such as upper sole,
whatever.
So to normalize it I thought of
Product
rodID, prodNumAttributes
rodID, attributeSkew:skewID, ProdID, skewNum, color
I am not sure this is it. It may need a parent child relationship in
product to attributes. Is there a way to get rid of the attributes
table and just have product and skew so it works also for the
clothing?
thanks,