[2.2.x] Fixed #30216 -- Doc'd that BooleanField is no longer blank=True in Django 2.1.
This commit is contained in:
parent
b1eea8a73a
commit
a6972e8854
|
@ -462,6 +462,10 @@ isn't defined.
|
||||||
use :class:`NullBooleanField` instead. Using the latter is now discouraged
|
use :class:`NullBooleanField` instead. Using the latter is now discouraged
|
||||||
as it's likely to be deprecated in a future version of Django.
|
as it's likely to be deprecated in a future version of Django.
|
||||||
|
|
||||||
|
In older versions, this field has :attr:`blank=True <Field.blank>`
|
||||||
|
implicitly. You can restore the previous behavior by setting
|
||||||
|
``blank=True``.
|
||||||
|
|
||||||
``CharField``
|
``CharField``
|
||||||
-------------
|
-------------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue