#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
-------------------------------------+-------------------------------------
Changes (by felixxm):
* status: assigned => closed
* resolution: => fixed
Comment:
We agree on [https://groups.google.com/forum/#!msg/django-
developers/pSvFXcUUkRs/i2XPuai3AwAJ the mailing list] that we should
deprecate only the model `NullBooleanField`.
--
Ticket URL: <https://code.djangoproject.com/ticket/31369#comment:13>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.bb1caf0881313cd0564913b9d15c6f8d%40djangoproject.com.
