m3rajk — Sun, 10 Aug 2003 18:44:36 +0000

i read soomewhere that the percent and decimal versions are less stable than the hex codes. so why would someone making a large site use anything but hex?

and for hex all you need is a char(6)
just use the fully qualified hex: '000000' through 'ffffff'

Mark Hensler — Fri, 08 Aug 2003 05:59:23 +0000

Hey nitin, I was remarking on your comment of enlarging the primary key from TINYINT to MEDIUMINT. I wouldn't expect anyone to store colors in an integer field unless they want a headache.

Suzanne — Fri, 08 Aug 2003 04:34:31 +0000

Why on earth would you not use hex/rgb instead of names? Names aren't even fully supported across the board?

I'll use the basics (black, white, blue, red, yellow, green, orange and purple) on occasion, but otherwise, it's hex/rgb in the CSS.

That said, if we're talking about product colours (i.e. the khaki sweater, or the kelly green sweater), then colour names are better. For that application, a table that only lists colour code and colour name would be best.

KandieMan101 — Fri, 08 Aug 2003 04:16:38 +0000

Quote:
That's just the standard web-design practice every experienced webmaster follows.

Could you please show me a large, well developed site that uses color names INSTEAD of color codes?

nitin — Fri, 08 Aug 2003 04:14:52 +0000

Hi Mark,

With all due respect to your thoughts, I believe the point is not about storing color codes. The question was only about storing 50 colors and if we are talking about websites, it's always better to choose web-safe colors. So, again using a name is a much better option than using color codes directly. That's just the standard web-design practice every experienced webmaster follows.

If you strictly want to design your table for codes, IMHO, then probably a better option is to use UNSIGNED INTEGER would be a better option.

Thanks,
- Nitin

Mark Hensler — Thu, 07 Aug 2003 07:39:42 +0000

MEDIUMINT is insane (24 bit), SMALLINT should be all you need (16bit). Unless we're going for 32bit True Color with an INT field.

Use appropriate column type

nitin — Thu, 07 Aug 2003 06:17:22 +0000

Looking at your requirement, you may be just fine with the following DDL

CREATE TABLE COLOR(
COLOR_ID TINYINT UNSIGNED NOT NULL,
COLOR_NAME VARCHAR(20),
PRIMARY KEY(COLOR_ID)
)

TINYINT should take you 255 color ids. If you think you need more, you can always alter the table to use MEDIUMINT.

Hope that helps,
- Nitin

Mark Hensler — Wed, 30 Jul 2003 21:38:09 +0000

What is this going to be used in? Are you looking for speed? To conserve space? Or simplicity in design?

druagord — Wed, 30 Jul 2003 21:34:50 +0000

i usually use a char(6) and store the color in ffffff format