Fixes #10786 -- Document that NullBooleanField should be used rather than BooleanField with null=True. Thanks sbj3 for the patch.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16020 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
ab9e596ca6
commit
91e59aeca0
|
@ -59,6 +59,9 @@ string, not ``NULL``.
|
||||||
coerced for string-based fields that have the empty string as a possible
|
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.
|
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.
|
||||||
|
|
||||||
``blank``
|
``blank``
|
||||||
---------
|
---------
|
||||||
|
|
||||||
|
@ -341,6 +344,9 @@ A true/false field.
|
||||||
|
|
||||||
The admin represents this as a checkbox.
|
The admin represents this as a checkbox.
|
||||||
|
|
||||||
|
If you need to accept :attr:`~Field.null` values then use
|
||||||
|
:class:`NullBooleanField` instead.
|
||||||
|
|
||||||
.. versionchanged:: 1.2
|
.. versionchanged:: 1.2
|
||||||
|
|
||||||
In previous versions of Django when running under MySQL ``BooleanFields``
|
In previous versions of Django when running under MySQL ``BooleanFields``
|
||||||
|
|
Loading…
Reference in New Issue