Results 1 to 3 of 3
  1. #1
    Join Date
    May 2003
    Posts
    1

    Question Unanswered: Product database design

    I'm working on a database to store information on products which my company sells.

    A summary of the basic information which is to be stored looks as follows:

    Books:
    Product ID number
    Title
    Author
    Blurb
    Size (dimensions)
    Publisher
    Book type (hardcover, paperback etc)
    Supplier
    Supplier's product ID
    .. and so on

    DVDs
    Product ID number
    Title
    Director
    Stars (featured actors)
    Running time (minutes)
    DVD technical features (DTS, Dolby, Widescreen etc)
    Encoding (region)
    Studio (film company)
    Supplier
    Supplier's product ID

    What I am basically wanting to know is, what would be the best way to build this database? Should I use seperate tables for different things or combine it all into one table? Should general information be stored in one table with seperate tables for the category-specific information?

    I would also like the database to be easily added to in the future - for example if we start selling other products - video games, music CDs etc.

    Thanks for any help.

  2. #2
    Join Date
    Jan 2003
    Location
    Vietnam
    Posts
    188

    Re: Product database design

    pls see the capital

    Originally posted by Womble
    I'm working on a database to store information on products which my company sells.

    A summary of the basic information which is to be stored looks as follows:

    Books:
    Product ID number
    Title
    Author
    Blurb
    Size (dimensions)
    Publisher
    Book type (hardcover, paperback etc)
    Supplier
    Supplier's product ID
    .. and so on

    DVDs
    Product ID number
    Title
    Director
    Stars (featured actors)
    Running time (minutes)
    DVD technical features (DTS, Dolby, Widescreen etc)
    Encoding (region)
    Studio (film company)
    Supplier
    Supplier's product ID

    What I am basically wanting to know is, what would be the best way to build this database? Should I use seperate tables for different things or combine it all into one table? SHOULD BE DIFFERENT TABLES Should general information be stored in one table with seperate tables for the category-specific information? A SEPERATE TABLE WILL WORKS

    I would also like the database to be easily added to in the future - for example if we start selling other products - video games, music CDs etc. SEPERATE TABLES FOR EACH CATEGORY SINCE THERE ARE NOT MANY COMMON FIELDS

    Thanks for any help.
    HOPE THIS HELPS
    qha_vn

  3. #3
    Join Date
    Mar 2003
    Posts
    8
    Personnaly I would create 2 tables:

    TABLE#1 (INDEX TABLE)-

    Product ID number
    ProductType (DVD, BOOK, CD....etc)
    Title
    Author\Director\Artist
    Supplier
    Supplier's product ID

    TABLE#2 (DATA TABLE)-

    Product ID number
    ProductType (DVD, BOOK, CD....etc)
    Blurb (blurb about book, technical features for the DVD's)
    Size (Book = pages, DVD = runningtime)
    Publisher (book publisher, film company, artist label for CD's)
    ....etc

    There would be more fields in table#2 , but they are up to you. Since all this sort of information has the same 'fields' you can give them general names and use the fields for each type of record. You just have to check the ProductType to make sure you are selecting the proper type (DVD, CD, Book).

    You could combine you ProductID and ProductType by using a pre-fix such as CD123456 or DVD987654. This is only a suggestion, and having the smaller index table allows you to search quicker once your DB fills up.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •