Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. Database Design

Database Design

Scheduled Pinned Locked Moved Web Development
databasedesignhelptutorial
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    Gjm
    wrote on last edited by
    #1

    I am developing an ecommerce website, aimed at selling electronic products. So for storing the product details I use a product table in which I have the fields for storing the product specifications. My problem is how to include the specifications of different products like motherboard, mouse, Monitor in a single table (product table). How should I design the product table to hold the specifications of different products. Suggest me a good database design for this problem.

    D 1 Reply Last reply
    0
    • G Gjm

      I am developing an ecommerce website, aimed at selling electronic products. So for storing the product details I use a product table in which I have the fields for storing the product specifications. My problem is how to include the specifications of different products like motherboard, mouse, Monitor in a single table (product table). How should I design the product table to hold the specifications of different products. Suggest me a good database design for this problem.

      D Offline
      D Offline
      David Mujica
      wrote on last edited by
      #2

      I don't recommend you save the specifcations in the same table as your products. This is a classic one to many relationship which should be implemented in two tables; it will be so much easier in the long run. For example: Product table PROD_ID Description other fields Specificaitons Spec_ID Prod_ID Description my 2 cents :cool:

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups