Closed ngnpope closed 4 years ago
The Django correctness section mentions using NullBooleanField instead of BooleanField(null=True). The reverse should now be advocated.
NullBooleanField
BooleanField(null=True)
Soft-deprecation in Django 2.1 (release notes, pull request) Hard-deprecation in Django 3.1 (release notes, pull request)
Yes it's in the release notes:
BooleanField can now be null=True. This is encouraged instead of NullBooleanField, which will likely be deprecated in the future.
BooleanField
null=True
https://docs.djangoproject.com/en/2.1/releases/2.1/#models
The Django correctness section mentions using
NullBooleanField
instead ofBooleanField(null=True)
. The reverse should now be advocated.Soft-deprecation in Django 2.1 (release notes, pull request) Hard-deprecation in Django 3.1 (release notes, pull request)