diff options
| author | David Vaz <davidmgvaz@gmail.com> | 2019-09-27 04:00:32 -0700 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2019-09-27 13:02:08 +0200 |
| commit | 1556a67c65c336ab12961c6123b129ac10e729b8 (patch) | |
| tree | e1dc1eafd4be13148b3bf1d948e3671cc69feda6 | |
| parent | db181f4b7ceac2a7050d462224bf5109dcd4790d (diff) | |
| download | django-1556a67c65c336ab12961c6123b129ac10e729b8.tar.gz | |
[2.1.x] Fixed #30216 -- Doc'd that BooleanField is no longer blank=True in Django 2.1.
Backport of a6972e88547ad5a51592f2b6d5046754c4b59394 from stable/2.2.x
| -rw-r--r-- | docs/ref/models/fields.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index ffd2387739..48980a92b4 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -459,6 +459,10 @@ isn't defined. use :class:`NullBooleanField` instead. Using the latter is now discouraged 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`` ------------- |