We're trying to figure out how to design a particularly critical table in
our database schema. The choices are to use a single large table or a
series of dynamically created small tables.
This table will receive the majority of traffic (queries and updates) in the
database so it's a key part of
www.etudes-marche.com
-Original Message-
From: Douglas Pearson [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 23, 2007 4:35 PM
To: mysql@lists.mysql.com
Subject: Dynamic tables--always a bad idea?
We're trying to figure out how to design a particularly
critical table in
our database
-Original Message-
From: Jerry Schwartz [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 23, 2007 2:02 PM
To: 'Douglas Pearson'; mysql@lists.mysql.com
Subject: RE: Dynamic tables--always a bad idea?
How are you going to do queries that join or merge thousands of tables? or
won't that be necessary
