On Jun 25, 3:06 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Consistency in API seems to imply that "null=True" should always works > and permits empty values to be stored. It also means fields without a > default need a value to be set.
You make a very good point. However I still think that it at least should be documented, that a BooleanField will not be saved, if not given either a default value or a value. E.g. "BooleanField: A true/ false field. NOTE: Unless null = True, this field requires value.". And I still think it's a bit much letting such a problem get all the way to the db. > I haven't looked at that ticket for a while, but I'm inclined to say > it's not a bug. What ever it is, my life would have been 30 minutes easier if it were documented, or transparent. -- 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 -~----------~----~----~----~------~----~------~--~---
