#10060: Multiple table annotation failure
----------------------------------------------+-----------------------------
Reporter: svsha...@intellecap.net | Owner:
Status: new | Milestone:
Component: ORM aggregation | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------------+-----------------------------
Comment (by thamedave):
Another victim.
This bug means that you can't use annotations at all unless you know
exactly what is going to happen to your QuerySet later. Functions cannot
expect that any QuerySet passed as a parameter is capable of being
annotated as it may already have been done.
I am a reasonably to Django, but it seems odd to me that this has remained
a known bug for 2 years without anyone working on it, or a the
documentation being changed to reflect the lack of functionality. I
understand russell's logic that bugs should not be documented, but if this
cannot be fixed, then surely it should be removed from intended behaviour.
--
Ticket URL: <http://code.djangoproject.com/ticket/10060#comment:27>
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.
