#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 terpsquared): Just ran into this. At the very least, the documentation should be updated to reflect this issue. https://docs.djangoproject.com/en/dev/topics/db/aggregation/#order-of- annotate-and-filter-clauses -- Ticket URL: <https://code.djangoproject.com/ticket/15049#comment:8> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/062.022ac00bb05b2525073c438710e0f23f%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.