#31624: Model.objects.all().delete() subquery usage performance regression
-------------------------------------+-------------------------------------
     Reporter:  Adam (Chainz)        |                    Owner:  Simon
  Johnson                            |  Charette
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  3.1
  (models, ORM)                      |
     Severity:  Release blocker      |               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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):

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


Comment:

 In [changeset:"972000420e08703dd4981466ff67adcd5a61ad4b" 97200042]:
 {{{
 #!CommitTicketReference repository=""
 revision="972000420e08703dd4981466ff67adcd5a61ad4b"
 Fixed #31624 -- Avoided subquery usage on QuerySet.all().delete().

 Thanks Adam Johnson for the report.

 Regression in 7acef095d73322f45dcceb99afa1a4e50b520479.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31624#comment:5>
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/068.a0d1ac147acda4dfc6d17037b08b8100%40djangoproject.com.

Reply via email to