Yes, it's a feature. TINYINT is a common workaround for the lack of BOOLEAN type with MySQL. There is a BIT type but, before v.5, it was only a synonym for TINYINT(1) (just like BOOLEAN is). Now, BIT is a totally different thing, and probably isn't a good choice for BOOLEAN anymore.
I'd love to suggest you move to Postgres but that comes with its own maddening BOOLEAN behaviour in that it returns the characters 't' or 'f' (really not PG's fault but a problem of accurately describing booleanness in any of a wide variety of client languages). On Fri, Feb 22, 2008 at 7:35 AM, timtrice <[EMAIL PROTECTED]> wrote: > > Are the writer's of CakePHP aware that for some reason, by default, if > you have a field in your db table set to tinyint with a length of 1 > that Cake processes it in form fields as booleans? This was a very > frustrating experience for me as I kept thinking it was something in > my programming. Finally I realized the only commonality was that the > fields to which could not be changed or seemingly were not saving what > I was telling it to were written in the DB as 1 character tinyint's. > When I changed those fields to a length of 2, my forms worked > normally. > > Just one, curious if anyone else has had that issue and 2, if Cake is > aware? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
