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
storing in rows or in one field
Moderator: General Moderators
-
shivam0101
- Forum Contributor
- Posts: 197
- Joined: Sat Jun 09, 2007 12:09 am
Re: storing in rows or in one field
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.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.
Could you add a boolean field to your table and merely set the value in the records to whom you have sent newsletters?