Hi.
I find that 1-to-1 relationships are often useful & appropriate, and they
would help you reduce the number of columns per row.
For instance in some db of people, addresses, salary info, medical info,
&c, ------although they could be jammed into one giant row per person, make
perfect sense in separate tables with a person-key linking rows in these
tables to rows in the person table in a one-to-one relationship.
This assumes these 248 piece of data have some logical internal structure
that would group them into sets that could describe some entity.
My 2 cents.
- Brian Hughes
Web Developer/Programme Analyst
LII, Cornell Law School
At 02:52 PM 1/25/2001 +0000, you wrote:
>hi,
>
>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
