#29725: Inefficient SQL generated when counting a ManyToMany
-------------------------------------+-------------------------------------
     Reporter:  Gavin Wahl           |                    Owner:  oliver
         Type:                       |                   Status:  new
  Cleanup/optimization               |
    Component:  Database layer       |                  Version:  master
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by felixxm):

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


Comment:

 Solution has been reverted because it caused the inconsistent behavior of
 `count()` and `exists()` on a reverse many-to-many relationship with a
 custom manager (see new tests in
 9ac8520fcde29840a1345be19d80dbda53aa6d03).

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29725#comment:14>
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.456b2506e451d16c3d81ac1205a59098%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to