It may become less readable on the server side, but if you
want to store lots of little bits of information, use a BIGINT
column as a collection of a bunch of bits ... pack and unpack
them in your application.
For searching, use the bitwise operators to do comparisons.
-Tilghman
--
"There cannot be a crisis today. My schedule is already full."
--Henry Kissinger
> -----Original Message-----
> From: anna soobrattee [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 26, 2001 08:52
>
> 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?
---------------------------------------------------------------------
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
