Database design input needed

programming
1

ok, I’m working on a relational database design for retailers-advertisers-products

Here is the current layout:

How would i design this to make it easier for other things i might want to do, like “all retailers who stock a product category”? or “all retailers a specific advertiser works with”?

Any SQL geeks?

2

bump

3

I have to admit, I saw this thread before your bump but didn’t reply because I couldn’t find much wrong with it.

It features a lot of joins but tbh that doesn’t really make a difference since joins are faster than the alternative.

It all looks structured and logic to me. If you are really concerned with the performance of your database, then maybe you should look into partitioning. I guess it’s a shameless self-promotion, but wrote a post of biblical length about sql performance here; http://www.erikhallander.com/blog/2008/web-server-performance-guide-part-23-mysql.html

Good luck!

4

lol, thanx for the input sekasi. I thought it was ok, i just threw it together, but I’m always one step behind common database design trends it seems.

5

I guess i’ll just make some stored procedures for my more common selects.