Browse files

Fixes #10786 -- Document that NullBooleanField should be used rather …

…than BooleanField with null=True. Thanks sbj3 for the patch.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent ab9e596 commit 91e59aeca0d4a554c418629999d1d9e758912c5c @SmileyChris SmileyChris committed Apr 6, 2011
Showing with 6 additions and 0 deletions.
  1. +6 −0 docs/ref/models/fields.txt
@@ -59,6 +59,9 @@ string, not ``NULL``.
coerced for string-based fields that have the empty string as a possible
value, and the value ``NULL`` will be stored to denote the empty string.
+If you want to accept :attr:`~Field.null` values with :class:`BooleanField`,
+use :class:`NullBooleanField` instead.
@@ -341,6 +344,9 @@ A true/false field.
The admin represents this as a checkbox.
+If you need to accept :attr:`~Field.null` values then use
+:class:`NullBooleanField` instead.
.. versionchanged:: 1.2
In previous versions of Django when running under MySQL ``BooleanFields``

0 comments on commit 91e59ae

Please sign in to comment.