#django.db.models.fields.related.RelatedManager.add>)
indicates that this would be incorrect implementation:
Using add() with a many-to-many relationship, however, will not call any
save() methods (the bulk argument doesn’t exist), but rather create the
relationships using QuerySet.bulk_cre
resources, even if it has no receivers;
> and as soon as you *do* connect a receiver, you consume even more
> resources. In the interests of performance, individual object signals
> on m2m operations are disabled in favor of the grouped m2m_changed
> signal.
I see, it makes sense for bat
n more
resources. In the interests of performance, individual object signals
on m2m operations are disabled in favor of the grouped m2m_changed
signal.
> * For m2m fields with auto_created intermediate model, calling
> ``Model.m2m_field.add/remove/clear`` sends m2m_changed. However addi
I'm wondering what was the rationale for introducing a new separate
signal for m2m relationships, as opposed to using the existing ones on
the intermediate ('through') model. Currently the situations is
confusing:
* For m2m fields with auto_created intermediate model, calling
``Model.m2m_field.add
