#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 |
----------------------------------------------+-----------------------------
Changes (by teemu):
* cc: teemu.kur...@iki.fi (added)
Comment:
Another victim here. Just spent several hours with finding this bug, which
had existed several days. This definitely should be either fixed or
prevented: values that the incorrect query provides are often somewhat in
the sensible range, depending on your row structures, which can make this
bug hard to spot.
I also tested both queries that bendavis78 outlined above and they give
correct results. Didn't do extensive performance testing yet, with 20K
rows in the largest table, both queries were between 0.05 and 0.10 secs.
--
Ticket URL: <http://code.djangoproject.com/ticket/10060#comment:26>
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-upda...@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.
