#18676: Django should do m2m deletes in a single query when possible
-------------------------------------+-------------------------------------
Reporter: Jeremy Dunck | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 1.4
(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
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"26c4be2ebe918601c0a13d4abb3f3cab49107c73" 26c4be2e]:
{{{
#!CommitTicketReference repository=""
revision="26c4be2ebe918601c0a13d4abb3f3cab49107c73"
Refs #18676 -- Enabled fast-delete for m2m_changed senders.
There's no reason to disable fast-delete when an intermediary
many-to-many model has connected m2m_changed receivers because the
signal is only sent when related manager's clear() and remove() methods
are directly called.
This must have been overlooked in 1cd6e04cd4f768bcd4385b75de433d497d938f82
given no regression tests fail when m2m_changed is not taken into
consideration to determine if fast-delete can be enabled.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/18676#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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.5a08fafecfae824487a6365c0a930194%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
