Thanks to everyone on this list in advance. Now, being that I don't know exactly how MySQL is implemented, I'm unsure of how to handle the following situation. I have a database foo, with: Table bar (every user would have a row... could be 100,000 rows): id, name, password (keyed on id and name) and Table wibble: (logged on users would have rows.... could be 0 to 100,000 rows): id, ip, url, timestamp (keyed on id and url) I need to: select id,password from bar where name=__ then verify password in code, and use the id to select/update stuff in table wibble and I also need to: select id from wibble where url=__ then, use id to select name from bar This database is going to be beaten with queries for these two tables. I am imagining that keeping these two tables in the same database is wise for performance, but what about the table separation? Would it be better to just throw the columns from table wibble into table bar as to avoid two queries? Or perhaps the search speed of MySQL is linear, so having a smaller table will speed up queries? *Any* comments on implementation would be much appreciated, Thanks, Zach Johnson --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
