#25754: queryset.distinct('field') doesn't raise "DISTINCT ON not supported"
when
it should
-------------------------------------+-------------------------------------
Reporter: yoyoma | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: distinct | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by yoyoma):
Hi charettes,
I appreciate the quick response, but I'm afraid you didn't read the entire
report. The queryset, in the context I've given, should have been
evaluated. See the first line of code in the first example.
--
Ticket URL: <https://code.djangoproject.com/ticket/25754#comment:3>
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/064.40da4d5d70474a97f3a3edb0ba4806ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
