#29725: Inefficient SQL generated when counting a ManyToMany
-------------------------------------+-------------------------------------
     Reporter:  Gavin Wahl           |                    Owner:  ontowhee
         Type:                       |                   Status:  closed
  Cleanup/optimization               |
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):

 * resolution:   => fixed
 * status:  assigned => closed

Comment:

 In [changeset:"66e47ac69a7e71cf32eee312d05668d8f1ba24bb" 66e47ac6]:
 {{{#!CommitTicketReference repository=""
 revision="66e47ac69a7e71cf32eee312d05668d8f1ba24bb"
 Fixed #29725 -- Removed unnecessary join in QuerySet.count() and exists()
 on a many to many relation.

 Co-Authored-By: Shiwei Chen <april.chen.0...@gmail.com>
 }}}
-- 
Ticket URL: <https://code.djangoproject.com/ticket/29725#comment:29>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018db117e676-0bc6ac95-ade7-42b2-b5b6-374ffca6905b-000000%40eu-central-1.amazonses.com.

Reply via email to