Answer by philipxy for Database Design with products, attributes and prices
Yes, you should "have something like products_prices_sizes". There is no reason not to. The design you give is encoding (product price, size) triplets as pairs of redundant pairs, ((product price),...
View ArticleAnswer by user2314737 for Database Design with products, attributes and prices
Something like this: each product and each size has an id, the prices table assigns a price to a pair (product_id, size_id)**products**----------id name1 orange juice**sizes**----------id size1 small2...
View ArticleDatabase Design with products, attributes and prices
What is the best approach to achieve product with multiple of prices and the prices depend on its attribute at the same time? I want to store orange juice (small) $10 and orange juice(large) $14. How...
View Article
More Pages to Explore .....
