Results 1 to 2 of 2
  1. #1
    Join Date
    Dec 2014

    Database design for price comparison site - too complex?

    I'm working on a regular price comparison site with two exceptions. I want to show price history and also allow users to subscribe to a product with a specific size and color. As a result, I've ended up with a somewhat complex database design and I'm afraid it will become both slow and difficult to manage (lots of join, etc.) when writing the functions.

    In the follow image you can see an outline I created with MySQLWorkbench:

    I'd really appreciate all feedback and thoughts.

  2. #2
    Join Date
    Jan 2007
    Can you have more than one price for a given product, from a certain merchant?

    Your attribute and property tables stink of EAV, which you need to be very careful with.

    Most people here are not a fan of that particular type of database design as its flaws often outweigh its flexibility benefit.

    P.S. don't confuse simplicity and complexity with right and wrong!
    Home | Blog

Posting Permissions

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