#11117: placeholder confusion when using aggregated query with extra
--------------------------------------+-------------------------------------
Reporter: slid...@web.de | Owner: nobody
Status: closed | Milestone:
Component: ORM aggregation | Version: 1.0
Resolution: duplicate | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* component: Database layer (models, ORM) => ORM aggregation
* needs_tests: => 0
* needs_docs: => 0
* resolution: => duplicate
Comment:
I'm going to close this as a dupe of #11104. It's not a literal duplicate
- the problem that is being described is different - but the underlying
cause (mishandling of SQL params) is the same. I'll put a link on #11104
to ensure that this problem is also fixed.
--
Ticket URL: <http://code.djangoproject.com/ticket/11117#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
