#10060: Multiple table annotation failure
----------------------------------------------+-----------------------------
Reporter: [email protected] | Owner:
Status: new | Milestone: 1.1
Component: ORM aggregation | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------------+-----------------------------
Comment (by bendavis78):
Ok, after spending several hours looking through
django/db/models/sql/query.py, I feel like my brain has turned to mush.
This is definitely better left up to the ppl that wrote it. I hope that
at some point someone who is capable can write a patch for it.
I'm against simply adding a "don't do this" in the documentation, because
users would simply expect something like this to work -- it's hard to
understand at a high level why simply adding another annotation from a
different relation would skew the results.
--
Ticket URL: <http://code.djangoproject.com/ticket/10060#comment:10>
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
-~----------~----~----~----~------~----~------~--~---
