A red flag is flying.
Usually, when people start talking about how the number of tables will multiply in an application, there is a problem with the design of data structures. If that's the case, now is the time to fix it.
Miles
At 05:35 PM 1/15/2004 +0000, Christian Calloway wrote:
Hey,
Sorry to post a mysql question here, but I wanted an answer from a PHP perspective. I am currently working on a database (for work) which contains 40 tables, and will continue to expand. The reason for expansion of tables is to obscure to get into, but the relationships all do make sence. I have never worked on anything over like 50 tables, and I was wondering if I should expect a performance hit, when say, I have 100 tables, 200 tables, etc. Would it be wiser to break up the logical sections into there own databases? Wouldn't that cause a bigger hit (to performance) with multiple tables from multiple databases being opened on every user query? Thanks in advance
Christian
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
