Thanks, that got me moving forward again. I've started experiencing erratic behavior though during my add() and edit() functions involving checkboxes. Using print_r on my $data array revealed that the checkbox was not only passing the value of 0 when a check is missing or is removed, but also passes "on" (when a check existed previously or was added) and "-1" (e.g. after a validation has failed, or the checkbox was unchecked and another field was modified).
The MySql field I'm using is tinyint with a length of 1 (signed <or not unsigned> *smile*). Tinyint interprets the 0 and "on" quite well, but is interpreting -1 as a 1. (This happens when a validation has failed, or the checkbox is unchecked and you modify another field.) I tried other lengths of tinyint, signing/unsigning tinyint, other datatypes, etc. and none of the others seem to really be compatible / work at all with a boolean setup. Is there a better datatype out there or is there a way to better configure tinyint to handle this situation? I wasn't able to locate an offical "boolean" datatype under the MySql docs. Thanks again, Devo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
