Garayed.com  

Go Back   Garayed.com > mySQL
FAQ Members List Calendar Search Today's Posts Mark Forums Read


Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 07-24-2006, 04:25 PM
roch77@gmail.com
 
Posts: n/a
Default breaking 1st Normal Form - Design Question

Hi,
I have to store multiple values of an attribute.
I won't be performing any manipulations on these, it will always stay
as a list.

Do you see any downside to keeping it as one field, as opposed to
creating another table,just to observe 1st Normal Form.

thanks
Roshan

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 07-24-2006, 05:14 PM
Peter H. Coffin
 
Posts: n/a
Default Re: breaking 1st Normal Form - Design Question

On 24 Jul 2006 08:25:39 -0700, roch77@gmail.com wrote:
> Hi,
> I have to store multiple values of an attribute.
> I won't be performing any manipulations on these, it will always stay
> as a list.
>
> Do you see any downside to keeping it as one field, as opposed to
> creating another table,just to observe 1st Normal Form.


If it's static, and you're not likely to want one value without the
others, then it's probably fine. There's several ways of picking up a
value from a field (full text search, FIND_IN_SET(), etc.). They're just
not hugely efficient, so if you REALLY don't want another table, and/or
won't be using the data in the column very much, it's okay to do it that
way.

--
_ o
|/)
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 08:33 AM.




LinkBacks Enabled by vBSEO 3.0.0 © 2007, Crawlability, Inc.