Re: neebee: on table designs.
| From: | Sebastian Mendel | Date: | Wed, 17 Nov 2004 17:03:27 +0000 |
| Subject: | Re: neebee: on table designs. | ||
| References: | 1 | Groups: | php.db |
| Request: | Send a blank email to php-db+get-37320@lists.php.net to get a copy of this message | ||
Phpnews wrote:
Hi All,1 table with clients 1 table with records -- Sebastian Mendel www.sebastianmendel.de www.warzonez.de www.tekkno4u.de www.nofetish.com www.sf.net/projects/phpdatetime www.sf.net/projects/phptimesheetI have 5000+ individual clients, each clients may have 100+ records.Each client can modify to their own records.In the order of maintenance, robustness, scalability then performance,which of the following do you think is best.i) 1 big table with 500000+ records ii) 5000+ small tables with 100+ records (1 table for each client)?At first I thought (i) but then for robustness a colleague pointed outthat on (ii) if clients screw up their own table it will not affect anyone else! any comments/suggestions are very much appreciated tony