> Part of me agrees with you, on a "Pure SQL level". but then why would
> anyone ever use ENUM or SET?
I wouldn't :-)
IMO, they're abominations that are to be avoided.
Now, ENUM could be a bit useful. The Pure SQL way to avoid those
would simply be a column of the right datatype and a CHECK constraint
(which MySQL doesn't support, yet).
--
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
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]
