#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
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"d91095def47a9916300b6f1ce970befcd497381f" d91095de]:
{{{
#!CommitTicketReference repository=""
revision="d91095def47a9916300b6f1ce970befcd497381f"
[3.1.x] Fixed #31624 -- Avoided subquery usage on QuerySet.all().delete().
Thanks Adam Johnson for the report.
Regression in 7acef095d73322f45dcceb99afa1a4e50b520479.
Backport of 972000420e08703dd4981466ff67adcd5a61ad4b from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31624#comment:6>
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.ee10102a5bc6aaf00b10bb1bdf5ff2be%40djangoproject.com.
