Date parsed: 18/10/2007 10:29:14
Date: Thu, 18 Oct 2007 08:29:14 +0200
I think another table would be the best thing. Your table has a foreign key to this and a row can
have any number of "color rows" associated with it.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi"WB" <none> wrote in message news:O7PuhuQEIHA.1208@TK2MSFTNGP05.phx.gbl...
> would one column of varchar values be better than one column each for red,
> green, blue?
>
> WB
>
> "Mohit K. Gupta" <mohitkgupta@msn.com> wrote in message
> news:65C7D9A4-9A96-414E-A917-7F595E7645C5@microsoft.com...
>> nvarchar is for Unicode characters. If you are just storing Hex values
> like
>> 00-FF? Then probably varchar is fine.
>>
>> --
>> Mohit K. Gupta
>> B.Sc. CS, Minor Japanese
>> MCTS: SQL Server 2005
>>
>>
>> "WB" wrote:
>>
>> > I want to store the Hex value of some color in a table. The table is a
> list
>> > of classifications and their associated color ([sick, red], [lunch,
> blue],
>> > etc.)
>> >
>> > How should I store the hex value in the column? nvarchar is the data
> type I
>> > have started with, but I wanted find out if there is something better?
>> >
>> > WB
>> >
>> >
>> >
>
>