#17210: Make NullBooleanSelect for NullBooleanField pass true/false as a GET
parameter
-------------------------------------+-------------------------------------
Reporter: anatoly techtonik | Owner: Basil
<techtonik@…> | Dubyk
Type: | Status: closed
Cleanup/optimization |
Component: Forms | Version: master
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: 1
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"35a08b8541c856a51b2ab718e0a2fe060debfa2a" 35a08b85]:
{{{
#!CommitTicketReference repository=""
revision="35a08b8541c856a51b2ab718e0a2fe060debfa2a"
Fixed #17210 -- Made NullBooleanSelect use unknown/true/false as query
data.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/17210#comment:6>
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/097.d22c319a800ed157b14d2f23a0494f27%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
