#29227: Allow BooleanField to be null=True
-------------------------------------+-------------------------------------
Reporter: Tim Graham | Owner: Tim
Type: | Graham
Cleanup/optimization | Status: closed
Component: Database layer | Version: master
(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 Tim Graham <timograham@…>):
In [changeset:"281c0223b376d6fa1a11e0726d824ed35cfe7524" 281c022]:
{{{
#!CommitTicketReference repository=""
revision="281c0223b376d6fa1a11e0726d824ed35cfe7524"
Refs #29227 -- Simplified NullBooleanField by making it subclass
BooleanField.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29227#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.3d85aff6446664e1c0763047ed5b83b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.