#29725: Inefficient SQL generated when counting a ManyToMany -------------------------------------+------------------------------------- Reporter: Gavin Wahl | Owner: oliver Type: | Status: closed Cleanup/optimization | Component: Database layer | Version: master (models, ORM) | Severity: Normal | Resolution: fixed Keywords: | Triage Stage: Accepted Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>): In [changeset:"e8de1cc94c9a251ba7c569468f1e94faf9a05671" e8de1cc9]: {{{ #!CommitTicketReference repository="" revision="e8de1cc94c9a251ba7c569468f1e94faf9a05671" [2.2.x] Fixed #30325 -- Reverted "Fixed #29725 -- Removed unnecessary join in QuerySet.count() and exists() on a many-to-many relation." This reverts commit 1299421cadc4fcf63585f2f88337078e43e660e0 due to a regression with custom managers. Backport of 5f7991c42cff73b6278106d499d719b726f85ead from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29725#comment:13> 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/067.e4ab82c81cecbd2de75d86608f731d57%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.