List:General Discussion« Previous MessageNext Message »
From:Sasha Pachev Date:July 6 1999 7:57pm
Subject:Re: Performace Tuning in MySQL
View as plain text  
"Geocrawler.com" wrote:
> 
> This message was sent from Geocrawler.com by "Rich" <rklein@stripped>
> 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.....
> 
> Richard
> 
> Geocrawler.com - The Knowledge Archive
> 

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

-- 
Sasha Pachev
http://www.sashanet.com/ (home)
http://www.direct1.com/ (work)
Thread
Performace Tuning in MySQLGeocrawler.com6 Jul
  • Re: Performace Tuning in MySQLSasha Pachev6 Jul
    • Re: Performace Tuning in MySQLOrlando Andico7 Jul
      • Re: Performace Tuning in MySQLMichael Widenius7 Jul
RE: Performace Tuning in MySQLJohn Foley8 Jul