>From: Martijn Tonies [mailto:m.tonies@stripped]
>Sent: Thursday, July 31, 2008 10:32 AM
>Subject: Re: SET vs. ENUM
>> >> Other than the fact that an ENUM can have many more values than a
>> >> there any particular reason to choose one over the other?
>> >Well, they are -different things- ...
>> >SETs shouldn't be used at all, IMO.
>> [JS] Why?
>It goes against normalizing your data, that's why.
>You cannot query them properly, that's why (just check the archives of
>You cannot add a possible value (same goes for ENUM) without a DDL
>statement, so "data" is intertwined with "metadata", which is bad.
>The metadata is not portable to other systems (neither is ENUM).
>> >ENUM can be somewhat useful, I guess.
>Need more reasons? :-)
[JS] No, you've made several good points. My reasoning is that inexperienced
folks using this table through MS Access don't generally understand enough
about database design to create the necessary JOINs to do it right. Perhaps
the trade-off is a bad one.
>Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB,
>MS SQL Server
>Database development questions? Check the forum!
>MySQL General Mailing List
>For list archives: http://lists.mysql.com/mysql
>To unsubscribe: http://lists.mysql.com/mysql?unsub=1