ENUM is MySQL-specific. ENUM fields in MySql are buggy anyway, ex. if you insert a non-enum value for a column that is set to not null, null will be inserted. Other db's use check constraints to enforce these kind of business logic issues. Because it's not possible to use the same mechanism for every database, I would suggest putting the logic in your peer classes. And continue to use not null and default values in your xml document. Search this list for the thread on InputValidator's. Dave Polito -----Original Message----- From: Daniel Rall [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 29, 2001 1:19 PM To: [EMAIL PROTECTED] Subject: Re: cache "robby" <[EMAIL PROTECTED]> writes: > Hi, > In mysql, if i have a column like > field enum('A','B','C') DEFAULT 'A' NOT NULL > what should be the matched xml? I'm not positive, but think that ENUM is MySQL-specific. Can anyone confirm this? We hit this same issue while porting to Torque and dealt w/ it by using a VARCHAR field w/ the ENUM's constants defined in a Java interface which we have our non-Base business objects implement. Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
