title: Database design for e-commerce site
body: <p>I am more of a frontend guy, so if these questions come out stupid, I apologize in advance :)</p>
  
  <p>I am designing a database schema for an e-commerce site. The product sold on this site can contain other products. Eq: Think of a car as a product. Car can also contain other products like seats, steering wheel, windshield, etc, each of which can be sold separately.</p>
  
  <p><strong>Question #1</strong>: What should <code>Product</code> table have to take this into account? Does it make sense for a <code>Product</code> table to have a field called <code>Products</code> that contain all the productIds associated with this product? (or normalized into its own table for optimization)</p>
  
  <p><strong>Question #2</strong>: This site will also have discounts every now and then that can be applied to a product (either on an individual product or a product that contains other products). There are also discounts that is applied to an entire order. What is the best approach to design the Discount table?</p>