#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
-------------------------------------+-------------------------------------
Changes (by charettes):
* status: new => closed
* resolution: => invalid
Comment:
Hi yoyoma,
As you might know `QuerySet` are lazily evaluated.
In this case Django needs to determine which backend will be used to run
the query against (e.g. routers can be involved) before raising the
`NotImplementedError`. That's the reason why the error will only be raised
at execution time.
--
Ticket URL: <https://code.djangoproject.com/ticket/25754#comment:2>
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.54e46edebfba0bea65a4821c3da2e2e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
