Re: Lots of tables Good or bad
| From: | Peter J. Krawetzky | Date: | Wed, 03 Jan 2001 13:15:28 +0000 |
| Subject: | Re: Lots of tables Good or bad | ||
| Groups: | php.db | ||
| Request: | Send a blank email to php-db+get-5555@lists.php.net to get a copy of this message | ||
Not sure what you mean? We have databases with thousands of tables. You
should have a one table for each representation of business data (unless you
denormalize).
-----Original Message-----
From: Trond Erling Hundal <webmaster@port-industry.com>
To: PHP-DB-LIST <php-db@lists.php.net>
Date: Wednesday, January 03, 2001 7:59 AM
Subject: [PHP-DB] Lots of tables Good or bad
>Hello and Hi.
>
>Happy new year everyone!
>
>I am currently administrating four different sites, all of which use the
>same database to manage content.
>We Use Mysql 3.22.32
>I have 31 tables in the database.
>Is this too much?
>
>(most of these tables are ready to be moved to different databases on the
>same server)
>
>- Trond
>
>
>--
>PHP Database Mailing List (http://www.php.net/)
>To unsubscribe, e-mail: php-db-unsubscribe@lists.php.net
>For additional commands, e-mail: php-db-help@lists.php.net
>To contact the list administrators, e-mail: php-list-admin@lists.php.net
>
>