If you are going to be needing to add columns and/or tables, you should
probably rethink your data model.
I'm not sure what data you are tracking, but perhaps you can
consolidate it a bit more. Make your columns into rows with a row type
field. A simple example would be tracking phone numbers. Instead of
having separate columns for home, work, and mobile, break it out into
another table so you can have unlimited phone numbers. Have a
descriptor field to indicate what type of phone number it is. You can
then add other phone type with ease, like beeper, fax, car, etc. This
also has the added advantage of being able to search on all phone
numbers in one query, yet also being able to search on just home phones.
On Wednesday, July 23, 2003, at 04:26 AM, Marek Lewczuk wrote:
Hello,
I have a table where misc data are stored. Right now this table has
about 30 columns, but for sure it will be more in the near future. So I
wonder how the big number (50-100) of table's columns affect for MySQL
DB performance. Maybe it's better to create more tables rather than
more
table's columns ??
--
Brent Baisley
Systems Architect
Landover Associates, Inc.
Search Advisory Services for Advanced Technology Environments
p: 212.759.6400/800.759.0577
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
