#15049: Using annotation before and after filter gives wrong results
-------------------------------------+-------------------------------------
Reporter: Alex | Owner: anonymous
Type: Bug | Status: assigned
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
Just a warning - this isn't at all easy to tackle. Basically if the query
has more than one "multijoin" then aggregates must be done either as
subselects or as subqueries.
An alternate is to just throw an error in such cases. Even this would be
better than producing wrong results silently.
--
Ticket URL: <https://code.djangoproject.com/ticket/15049#comment:7>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.0239aebe5aef4fdee62a0450048bef0e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
