#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
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"5fa4f40f45fcdbb7e48489ed3039a314b5c961d0" 5fa4f40f]:
{{{
#!CommitTicketReference repository=""
revision="5fa4f40f45fcdbb7e48489ed3039a314b5c961d0"
Fixed #29227 -- Allowed BooleanField to be null=True.
Thanks Lynn Cyrin for contributing to the patch, and Nick Pope for review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29227#comment:2>
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.9d90f219f7bfdbbd3ee04e9afccc61a3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
