Try both designs, fill them with lots of test data and benchmark the performance.
Also use EXPLAIN SELECT (a MySQL command which gives you information about how it is going to execute the actual SELECT command).
I read about this stuff in MySQL Reference Manual, published by O'Reilly Community Press.
Amir Hardon wrote:
Hi,
I'm planning a DB structure for an e-commerce system, and facing some question about the DB efficiency that I don't know how to approach.
For example what will be better, storing all items information in one table with one column for category, or having a separate items table for each category.
My guess is that separate tables will be faster for use but will consume more disk space.
Where can I learn about this subject? I guess it also depends on the DB backend I'm using, so for this case it is mySQL.
--- Omer My blog is at http://www.livejournal.com/users/tddpirate/
My opinions, as expressed in this E-mail message, are mine alone. They do not represent the official policy of any organization with which I may be affiliated in any way. WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html
================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
