Be careful about burying list type of data in a column.
I've seen poor performance issues parsing lists and XML type data
buried in columns.
A lot depends on your application and how and what you need to query
from those lists.
I've seen a case where a submitted documents were stored in a column
as an XML doc where the application had to fetch all the submissions
within the group and parse them in order to figure out who the
submitters were. This was being done at the gateway page of that tool.
It was a performance nightmare.
An alternative might be to store the integers vertically in a table
with a column describing the position of the value within the list.
Kinda off the cuff but something to think about.
On Wed, Sep 16, 2009 at 5:29 PM, John Meyer <john.l.meyer@stripped> wrote:
> Pete Wilson wrote:
>> Hi folks --
>> What would be the right approach in MySql 5.0?
>> My table, USERS, has columns NAME and IP. Associated with each user is
>> also a collection of from 0 to 50 INTs. What's a reasonable way to put these
>> 50 INTs in the table without using 50 separate columns, INT01...INT50? Is
>> BLOB an OK approach?
>> I have to manipulate these INTs in my CGI code.
>> -- Pete
> Break them out into a separate table linked via the primary key.
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1