#29615: Document difference in behaviour between m2m_changed behaviour for
add() vs
remove() when called multiple times.
-------------------------------------+-------------------------------------
Reporter: nirmalraghavan | Owner: Sanyam
Type: | Khurana
Cleanup/optimization | Status: closed
Component: Documentation | Version: 2.0
Severity: Normal | Resolution: duplicate
Keywords: signals, | Triage Stage: Accepted
m2m_changed |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: assigned => closed
* resolution: => duplicate
Comment:
As far as I can tell, the report that the `m2m_changed` signal isn't sent
for redundant `add()` calls isn't correct. The signal is still sent on any
subsequent `add()`, but `pk_set` is empty. This looks like a duplicate of
#27462.
--
Ticket URL: <https://code.djangoproject.com/ticket/29615#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 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/072.0b893d658ed5c622ed8b2a42379e7526%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
