#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 GitHub <noreply@…>):
In [changeset:"3b62d8c83e3e48d2ed61cfa32a61c56d9e030293" 3b62d8c]:
{{{
#!CommitTicketReference repository=""
revision="3b62d8c83e3e48d2ed61cfa32a61c56d9e030293"
Refs #31369 -- Improved hint message in NullBooleanField's deprecation
warning.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31369#comment:15>
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/01070187ddc5caad-80f5e6d7-110c-48f5-9cf2-3a622d5d8b56-000000%40eu-central-1.amazonses.com.
