RE: [PHP-DB] neebee: on table designs.

From: Date: Wed, 17 Nov 2004 14:33:28 +0000
Subject: RE: [PHP-DB] neebee: on table designs.
Groups: php.db 
Request: Send a blank email to php-db+get-37317@lists.php.net to get a copy of this message
small tables are easier to maintain and grow and quicker to search. need more info about the data to really help. probably 1 main clients table with basic info and then 1 or more smaller tables that hold certain specifics bastien
From: "phpnews" <tony.yau@emigen.co.uk> To: php-db@lists.php.net Subject: [PHP-DB] neebee: on table designs. Date: Wed, 17 Nov 2004 07:05:27 -0000 Hi All,
    I 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 out
that on (ii) if clients screw up their own table it will not affect anyone else! any comments/suggestions are very much appreciated tony -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php


« previous php.db (#37317) next »