SEO

#1 (**permalink**) 02-28-2008, 07:58 AM

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

#2 (**permalink**) 02-28-2008, 07:58 AM

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
|/)

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

breaking 1st Normal Form - Design Question