#32663: Remove Error raising on annotation & distinct call
-------------------------------------+-------------------------------------
Reporter: Yovel Cohen | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: SQLCompiler ORM | Triage Stage:
Query | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
There's a valid reason why this error is raised as explained in these
comment https://code.djangoproject.com/ticket/6422#comment:59; it's less
about the validity of the generated SQL and more about the correctness of
the returned results.
Given the rare cases where mixing aggregation and distinct is necessary
and the complexity involved in ''getting it right'' I'm of opinion that we
should keep disallowing it.
--
Ticket URL: <https://code.djangoproject.com/ticket/32663#comment:4>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.aa32dcc9f156f445fbc1f5613a5bc619%40djangoproject.com.
