5 messages in com.mysql.lists.win32Re: getting ENUM values| From | Sent On | Attachments |
|---|---|---|
| Michael Weber (Infospace Inc) | 22 May 2001 09:06 | |
| leo g. divinagracia iii | 23 May 2001 18:12 | |
| Stefan Schmiedl | 24 May 2001 01:19 | |
| Sinisa Milivojevic | 24 May 2001 03:20 | |
| PeterWR | 24 May 2001 04:26 |
| Subject: | Re: getting ENUM values![]() |
|---|---|
| From: | Stefan Schmiedl (s...@xss.de) |
| Date: | 05/24/2001 01:19:58 AM |
| List: | com.mysql.lists.win32 |
+---------+------------------------- | from | leo g. divinagracia iii <ldiv...@csuhayward.edu> | to | <> | date | 24.05.2001 03:13 | subject | getting ENUM values +---------+-------------------------
l> i would too... doesnt the ENUM type violate one of the normalization l> rules?
In real life, you can often get away with compromises :-)
l> plus, i find it easier to admin tables like that. now i dont know how l> MYSQL stores the actual data, so space-wise, it's smaller to store a "1" l> than "corporate" especially if you have lots and lots of data...
there is a limit on possible enum values ... section "7.3.1.3 Storage requirements for string types" to be exact. There are at most 65536 different enum values possible and only 1 or two bytes are stored, depending on how many values you have specified.
So, actually, enums are *efficient*.
Regards, Stefan Zeos Documentation
ZEOS - Open source Delphi components for SQL servers http://www.zeoslib.org What do you want to see in an FAQ for Zeos? Drop me a line at ze...@xss.de
-- DTSTTCPW OAOO, since YAGNI more often.




