On Thu, May 14, 2009 at 1:51 AM, John Andersen <[email protected]> wrote: > > Hi Brian, > > I agree that NULL can be used, if you are not specifically tracking/ > looking for a "Not answered" value. > > If the specification is to have the possibility to know that a field > has the value of either "Not answered", "No", "Yes", then I will > always define all the valid values (the domain), never relying on a > NULL in my range of "values" :) > That way I will not have a problem, when later some bright head higher > in the organization hierarchy, decides that we need a "Not applicable" > value. If I already assumed that NULL equals "Not answered" I would > now have a problem!
I hear ya. I suppose one could add the 3rd column at that point, then update the table to change all NULLs to -1 or something like that. > But that is an aside from what the OP asked for, so sorry for that. > > If I remember correctly, does CakePHP also create the dummy input > checkbox for the radiobuttons? And are they the reason for CakePHP > saving a 0 value when not selecting either radiobuttons? Maybe you > know Brian? You might have something there. I'm trying to think of something I've done with radio buttons. I'm sure that I have. If I think of it, I'll check. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~----------~----~----~----~------~----~------~--~---
