Jerry, > >> Other than the fact that an ENUM can have many more values than a SET, > >is > >> 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 this list). 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? :-) Martijn Tonies Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle & MS SQL Server Upscene Productions http://www.upscene.com My thoughts: http://blog.upscene.com/martijn/ Database development questions? Check the forum! http://www.databasedevelopmentforum.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
