#11916: Extra params + aggregation creates incorrect SQL.
---------------------------------------------------+------------------------
Reporter: [email protected] | Owner: nobody
Status: new | Milestone: 1.2
Component: Database layer (models, ORM) | Version: 1.1
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by ikelly):
Oracle doesn't allow column aliases from the select list in the "group by"
clause. This is the reason that we repeat the subquery rather than use
the alias. The alternative would be to define the column aliases in a
subquery in the "from" clause, which adds complexity.
But I don't think that's necessary. It appears to me that the only thing
wrong here is that in this case the "group by" subquery isn't getting
parenthesized as it should.
--
Ticket URL: <http://code.djangoproject.com/ticket/11916#comment:13>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
