#31369: Deprecate the model NullBooleanField.
-------------------------------------+-------------------------------------
Reporter: David Smith | Owner: Hristiyan
Type: | Ivanov
Cleanup/optimization | Status: closed
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"d992f4e3c29a81c956d3d616f0bc19701431b26e" d992f4e]:
{{{
#!CommitTicketReference repository=""
revision="d992f4e3c29a81c956d3d616f0bc19701431b26e"
Refs #31369 -- Removed models.NullBooleanField per deprecation timeline.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31369#comment:14>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.0999585054013d8e449353e50962af3e%40djangoproject.com.
