#32515: m2m_changed signal not received with custom through model
-------------------------------------+-------------------------------------
Reporter: leon hughes | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: m2m_changed, | Triage Stage:
signal, custom model, | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
The `m2m_changed` signal was created for automatically created
intermediate models. If you have an explicit `through` model, you can
attached `Model` signals to it, i.e. `pre_save`, `post_save`,
`pre_delete`, and `post_delete`.
--
Ticket URL: <https://code.djangoproject.com/ticket/32515#comment:3>
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/067.8185f25059f4906d21e5c64da095aaed%40djangoproject.com.
