1
0
mirror of https://github.com/django/django.git synced 2025-10-24 06:06:09 +00:00

Refs #31369 -- Deprecated models.NullBooleanField in favor of BooleanField(null=True).

This commit is contained in:
Tim Schilling
2020-03-30 21:16:33 -05:00
committed by Mariusz Felisiak
parent 34a69c2458
commit a92cc84b4a
7 changed files with 37 additions and 2 deletions

View File

@@ -202,6 +202,8 @@ Model fields
in historical migrations.
* **fields.W902**: ``FloatRangeField`` is deprecated and will be removed in
Django 3.1. *This check appeared in Django 2.2 and 3.0*.
* **fields.W903**: ``NullBooleanField`` is deprecated. Support for it (except
in historical migrations) will be removed in Django 4.0.
File fields
~~~~~~~~~~~

View File

@@ -1182,8 +1182,11 @@ values are stored as null.
.. class:: NullBooleanField(**options)
Like :class:`BooleanField` with ``null=True``. Use that instead of this field
as it's likely to be deprecated in a future version of Django.
Like :class:`BooleanField` with ``null=True``.
.. deprecated:: 3.1
``NullBooleanField`` is deprecated in favor of ``BooleanField(null=True)``.
``PositiveBigIntegerField``
---------------------------