#15959: .values()/.values_list() fails on EmptyQuerySet
-------------------------------------+-------------------------------------
Reporter: Davide Rizzo | Owner: nobody
<mail@…> | Status: closed
Type: Bug | Version: 1.2
Component: Database layer | Resolution: fixed
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: dceu2011 | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by Anssi Kääriäinen <akaariai@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"69a46c5ca7d4e6819096af88cd8d51174efd46df"]:
{{{
#!CommitTicketReference repository=""
revision="69a46c5ca7d4e6819096af88cd8d51174efd46df"
Tests for various emptyqs tickets
The tickets are either about different signature between qs.none() and
qs or problems with subclass types (either EmptyQS overrided the custom
qs class, or EmptyQS was overridden by another class - values() did
this).
Fixed #15959, fixed #17271, fixed #17712, fixed #19426
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/15959#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
