Hi. Having looked at #2855 and wondered the resolution of that ticket, i wanted to raise the discussion again.
To me, and many others, it makes absolutly no sense, that a BooleanField with no default value given, sould yield a SQL error uppon saving it. The ticket states that a BooleanField should be given a default value of False, and that null's should not be allowed, and I can only say that i agreed with that. After all, that is what NullBooleanField is there for - right? If anyone can think of a valid reason for a bool to be '' (not null, not true, not false, but en empty string) please do speak up :) -- Mads Sulau Joergensen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
