Models with a BooleanField are instantiated with that field's value set to False if no default or initial value is provided. Instead, like most other fields, the field's initial value should be set to None. This None should be left uncoerced when attempting to save the instance, so attempting to save should result in a database error for trying to set null on a non-null field.
Although this change is backwards incompatible, that depends how far backwards you go. Apparently the behavior was as I think it should be at the time #2855 was created. The facts that (1) the behavior has changed, and (2) #2855 was wontfix'd together make a strong case that this should be considered a bug, and therefore should be changeable immediately despite being backwards incompatible. Links: http://code.djangoproject.com/ticket/15124 http://code.djangoproject.com/ticket/2855 -- 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.
