5 messages in com.mysql.lists.mysqlRe: Performace Tuning in MySQL
FromSent OnAttachments
Geocrawler.com05 Jul 1999 19:57 
Sasha Pachev06 Jul 1999 12:56 
Orlando Andico07 Jul 1999 07:01 
Michael Widenius07 Jul 1999 08:41 
Foley, John08 Jul 1999 12:48 
Subject:Re: Performace Tuning in MySQL
From:Sasha Pachev (sas@direct1.com)
Date:07/06/1999 12:56:43 PM
List:com.mysql.lists.mysql

"Geocrawler.com" wrote:

This message was sent from Geocrawler.com by "Rich" <rkl@icorp.com> Be sure to reply to that address.

I am creating a database to enable users to store a variety of their preferences
as well as storing various search results to build a MyFavorites section for the
site. The data will be retrieved used PHP3.

Situation: ======== Users enter various search criteria and the database returns all relevant vendor
names. The users can then click a check-box next to the vendor name to save it
in "MyFavorites".

Question: ======== Is it better to store the favorites in one field of the USER table as a
concatenated list of store id's (i.e. 1111:1235:54320:1257) and parse the list
when retrieving or should the database be normalized by creating a composite
table for the two entities?

Thanks for any suggestions.....

You should normalize. I cannot think of a situation when it would not be good to normalize, can anyone ?