Michael Dykman wrote:
I hope I'm not opening an old can of worms here, but there are some
design trade-offs in this decision. ENUM has the strong advantage of
being able to constrain the contents to the specific expected values. It is not possible for an application insert an illegal value whereas
using INT one would have to explicitly add a contraint to accomplish the
same thing .
You have essentially the same problem with ENUM:
| If you insert an invalid value into an |ENUM| (that is, a string not present in the
| list of allowed values), the empty string is inserted instead as a special error
| value. This string can be distinguished from a ``normal'' empty string by the
| fact that this string has the numerical value 0.
See http://dev.mysql.com/doc/mysql/en/ENUM.html
-- Keith Ivey <[EMAIL PROTECTED]> Washington, DC
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
