#18414: queryset.exists() returns False when queryset is distinct and sliced
-------------------------------------+-------------------------------------
Reporter: bitrut | Owner: err
Type: Bug | Status: assigned
Component: Database layer | Version: 1.4
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: orm | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
The pull request doesn't seem to do what Luke asked - it disallows the
usage in any filtered situation, not just in conjunction with .distinct().
It seems likely there are users relying on this currently.
As for fixing the distinct() + limit + .exists() - it should be done by
not doing select distinct(1) but instead select distinct {normal select
fields} instead. I wonder if this would be straightforward to do?
--
Ticket URL: <https://code.djangoproject.com/ticket/18414#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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
