Also, here is a GREAT article on database normalization .. it should help you out ... it can get crazy ... a good balance between normalization and realization is good :)
http://www.phpbuilder.com/columns/barry20000731.php3 Paul Giesenhagen QuillDesign > There are a great many books ... > I would layout a product table that has the basics for all the products > > productTable > productId, Title, image, sku, price > > optionTable > optionId, optionTitle > > optionValues > optionValueId, optionId, optionValue, additionalPrice > > That is just for your product and options ... not departments and such. > > Basically you have a table for your products, a table for your options, and > a table for your option values. > > Hope this helps > > Paul Giesehagen > QuillDesign > > > > > Quick question. Are there any books or articles out there that describe > > best practices for laying out product in a database? > > > > Say you have product like a t-shirt. You could layout a relational > > database like this, but is this the best method? Should sizes, and > > colors have their own table? > > > > Category > > T-shirts > > > > SubCategory > > Long Sleeve T-Shirts > > Short Sleeve T-Shirts > > > > Product > > Sears T-Shirt > > Lands End T-Shirt > > > > ProductOptions > > Blue Lands End T-Shirt L > > Blue Lands End T-Shirt XL > > Green Lands End T-Shirt XL > > > > I suppose this is a pretty tough question that may not have a cut and > > dry answer seeing how all product seem to have all kinds of different > > options and structure.... > > > > > ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
