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 . The drawback is that ENUM is not standard SQL making your application non-portable to other RDBMS.
On Fri, 2004-07-30 at 08:14, Cemal Dalar wrote: > There was a discussion about this topic at past. Check the previous posts.As > a simple answer they are technically the same. Use what ever you want.. > > > Best Regards, > Cemal Dalar a.k.a Jimmy > System Administrator & Web Developer > http://www.dalar.net > > ----- Original Message ----- > From: "Salzgeber Olivier" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, July 30, 2004 12:48 PM > Subject: Enum or Int > > > > Hello all > > > > I have a table with a field which needs to hold a yes/no or 1/0 value. > > > > Which field type is best for this ? > > Should i create a ENUM field with yes or no values or is it better to > create > > an Int field for this ? > > > > What would you recommend ? > > > > Best regards > > Olivier Salzgeber > > > > -- > > MySQL General Mailing List > > For list archives: http://lists.mysql.com/mysql > > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > > > -- - michael dykman - [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
