Page 1 of 1

storing in rows or in one field

Posted: Sun Sep 16, 2007 9:25 pm
by shivam0101
Hello,

I am sending newsletters to a set of selected members who are randomly choosen. I want to store their ids wheneven i send to keep track. Should i have to store each one of their ids in a new row? or in one field itself using a (,). If i am storing in a new row, will the database will become slow? Please lete me know if their is any other better way of doing it.

Thanks

Posted: Sun Sep 16, 2007 9:32 pm
by feyd
New rows. Not for quite some time, generally.

Re: storing in rows or in one field

Posted: Mon Sep 17, 2007 2:38 pm
by califdon
shivam0101 wrote:I am sending newsletters to a set of selected members who are randomly choosen. I want to store their ids wheneven i send to keep track. Should i have to store each one of their ids in a new row? or in one field itself using a (,). If i am storing in a new row, will the database will become slow? Please lete me know if their is any other better way of doing it.
Avoid ever storing "non-atomic" values in a field ("atomic" values are values that cannot be logically broken into sub-values). It violates a primary rule of normalization.

Could you add a boolean field to your table and merely set the value in the records to whom you have sent newsletters?