#19426: EmptyQuerySet.distinct does not have the same signature as
QuerySet.distinct()
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: claudep
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution: fixed
Severity: Normal | Triage Stage: Ready for
Keywords: | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Anssi Kääriäinen <akaariai@…>):
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/19426#comment:9>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
