#10962: GROUP BY generation and extra seems to be too greedy
---------------------------------------------------+------------------------
Reporter: brosner | Owner: nobody
Status: closed | Milestone: 1.1
Component: Database layer (models, ORM) | Version: SVN
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by russellm):
* status: new => closed
* resolution: => invalid
Comment:
Your thinking is correct. Any extra(select=) columns are assumed to be
non-aggregates, and are therefore included in the GROUP BY; it is assumed
that if you need an aggregate in the extra, you can use annotate() and a
custom aggregate.
--
Ticket URL: <http://code.djangoproject.com/ticket/10962#comment:2>
Django <http://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 django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
