Author: SmileyChris
Date: 2011-04-06 03:33:32 -0700 (Wed, 06 Apr 2011)
New Revision: 16020
Modified:
django/trunk/docs/ref/models/fields.txt
Log:
Fixes #10786 -- Document that NullBooleanField should be used rather than
BooleanField with null=True. Thanks sbj3 for the patch.
Modified: django/trunk/docs/ref/models/fields.txt
===================================================================
--- django/trunk/docs/ref/models/fields.txt 2011-04-06 10:12:21 UTC (rev
16019)
+++ django/trunk/docs/ref/models/fields.txt 2011-04-06 10:33:32 UTC (rev
16020)
@@ -59,6 +59,9 @@
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.
+
``blank``
---------
@@ -341,6 +344,9 @@
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``
--
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.
