#25754: queryset.distinct('field') doesn't raise "DISTINCT ON not supported"
when
it should
-------------------------------------+-------------------------------------
Reporter: yoyoma | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
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):
charettes,
Thanks for looking into this. I decided to page through the
[https://github.com/ipython/ipython/issues?page=6&q=milestone%3A3.0+is%3Aclosed
3.0 release issues] (55 pages!) on GitHub, searching each page for
"exception". Perhaps a Google search would have been easier, but I found
the following:
1. https://github.com/ipython/ipython/issues/6384
2. https://github.com/ipython/ipython/pull/6394
I haven't had a chance to look through them completely (gotta run some
errands), but I wanted to add them in the meantime.
--
Ticket URL: <https://code.djangoproject.com/ticket/25754#comment:12>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.b8082bb264db50f9a01136da93c6fb20%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
