Hello Anna,
According to the MySQL Crash-Me the maximum numbers for 3.23.xx are:
- Columns in table 3398
- max table row length (without blobs) 65534
- table row length with nulls (without blobs) 65502
If you understand the concepts of DB normalization don't bother reading the
following:
300+ columns seems like a lot of columns for member information. Are you
sure you can't normalize your DB a little more by grouping or data into
relevant tables?
Example:
table members:
id | first | last | job_1 | job_2 | job_3 | job_4 |
You could create another table called jobs and your resulting tables would
look like:
table members
mem_id | first | last |
table jobs
job_id | mem_id | job | job_no |
Regards,
-Scott
> i've been asked to design a for a new web-based system which
> stores lots of data on it's members. There are currently about
> 500,000 member records.
>
> the problem is that i have to store at least 248 pieces of
> information on each user. i've made the system as relational as
> possible so that for each user record, i am only storing
> integers, for the most part tinyints and smallints.
>
> Is there a limit on the number of fields per record. I can
> easily see this new system requiring 300 fields(columns). what
> are the consequences for making a table with so many columns.
> this table will be updated very frequently - will access time
> degrade severely even though i use mainly ints in this table?
>
> thanks for your help.
> anna
>
>
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
