#5563: BooleanField should raise an error if null=True
--------------------------------------------+-------------------------------
Reporter: shaunc <[EMAIL PROTECTED]> | Owner: nobody
Status: new | Component:
Serialization
Version: SVN | Resolution:
Keywords: | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------------+-------------------------------
Changes (by shaunc <[EMAIL PROTECTED]>):
* has_patch: 1 => 0
* summary: BooleanField can be None if null=True => BooleanField should
raise an error if null=True
Comment:
um... well, how about that: I never noticed NullBooleanField before. I'd
close this, but I'll leave it up to others to decide if the following
should be done so others don't go astray:
1) doc for BooleanField should mention that one should use
NullBooleanField rather than null=True.
2) passing null=True to BooleanField init should cause an exception to be
raised (whose error text says: "use NullBooleanField")
--
Ticket URL: <http://code.djangoproject.com/ticket/5563#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
