#10060: Multiple table annotation failure
----------------------------------------------+-----------------------------
Reporter: [email protected] | 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 russellm):
The milestone was deleted because this is a fairly big problem, without an
obvious (or particularly easy) solution. There is no potential for data
loss, and there is a viable workaround - either "don't do it",or use two
queries rather than one. One of the side effects of a time-based release
schedule is that some bugs will always exist in releases - unfortunately,
this is one of those bugs.
Regarding adding this to a "known bugs" section - we don't document bugs.
We document intended behavior. The ticket tracker is for bugs.
--
Ticket URL: <http://code.djangoproject.com/ticket/10060#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
-~----------~----~----~----~------~----~------~--~---
