#33759: Using subquery to filter a model delete generates a sub-optimal SQL
-------------------------------------+-------------------------------------
Reporter: Christofer Bertonha | Owner: Aman
Type: | Pandey
Cleanup/optimization | Status: closed
Component: Database layer | Version: 4.0
(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@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"0b0998dc151feb77068e2387c34cc50ef6b356ae" 0b0998dc]:
{{{
#!CommitTicketReference repository=""
revision="0b0998dc151feb77068e2387c34cc50ef6b356ae"
Fixed #33759 -- Avoided unnecessary subquery in QuerySet.delete() with
self-referential subqueries if supported.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33759#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070187d69dcf00-bc72e10e-85f3-4108-8b50-6df6755056a6-000000%40eu-central-1.amazonses.com.
