Answer by S.Lott for Designing an 'Order' schema in which there are disparate...
There's no magic bullet that you've overlooked.You have what are sometimes called "disjoint subclasses". There's the superclass (Product) with two subclasses (ProductX) and (ProductY). This is a...
View ArticleAnswer by Bill Karwin for Designing an 'Order' schema in which there are...
The first solution you describe is the best if you want to maintain data integrity, and if you have relatively few product types and seldom add new product types. This is the design I'd choose in your...
View ArticleAnswer by Jared for Designing an 'Order' schema in which there are disparate...
Chris and AJ: Thanks for your responses. The product line may change, but I would not term it "volatile". The reason I dislike the third option is that it comes at the cost of metadata for the product...
View ArticleAnswer by AJ. for Designing an 'Order' schema in which there are disparate...
Does your product line ever change?If it does, then creating a table per product will cost you dearly, and the key/value pairs idea will serve you well. That's the kind of direction down which I am...
View ArticleAnswer by Chris Cudmore for Designing an 'Order' schema in which there are...
This might get you started. It will need some refinement Table Product ( id PK, name, price, units_per_package)Table Product_Attribs (id FK ref Product, AttribName, AttribValue)Which would allow you to...
View ArticleDesigning an 'Order' schema in which there are disparate product definition...
This is a scenario I've seen in multiple places over the years; I'm wondering if anyone else has run across a better solution than I have...My company sells a relatively small number of products,...
View Article
