#33403: Annotate results change when filtering *after* the annotate
-------------------------------------+-------------------------------------
Reporter: karyon | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: closed => new
* type: Uncategorized => Cleanup/optimization
* resolution: invalid =>
* stage: Unreviewed => Accepted
Comment:
While I'm not sure how to word this properly myself I also agree that the
''the annotation is computed over the state of the query up to the point
where the annotation is requested'' statement can be misleading without
context about how multi-valued filtering behaves.
Given we've recently revised the latter's documentation
(6174814dbe04fb6668aa212a6cdbca765a8b0522) I'm re-opening this ticket to
investigate doing the same here.
Maybe a single addition to docs about how multi-valued filtering against a
previously annotated aggregation might still yield duplicate results would
be enough?
--
Ticket URL: <https://code.djangoproject.com/ticket/33403#comment:6>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.7f05b5612481262555ddc20614af84f4%40djangoproject.com.
