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: