In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] writes: > I would suggest that if you want to compare against FALSE that you make > that one of your enumerated values. I would also make FALSE your default > value and the field not nullable. That way you don't have 3 possible > values to compare against in your field (null, empty string, and 1). If > you need three values (like: true, false, don't know) then make 3 enum > values. But, regardless of the contents of your ENUM list, I would still > make an ENUM field as "NOT NULL" and would set its default value to one > of its enumerated values. That way, the field should only hold what I said > it could hold.
I agree except that I wouldn't use an ENUM for that. Firstly, it's nonstandard, and secondly, there's a column type which explicitly says what you want, namely BOOL. (Well, it maps to a TINYINT, but that's another story...) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
