Changes between Version 1 and Version 2 of Ticket #17688, comment 19


Ignore:
Timestamp:
Feb 28, 2024, 4:32:20 PM (3 months ago)
Author:
Gary Chen

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #17688, comment 19

    v1 v2  
    11Interested in taking on this change. I'm thinking it'll involve undoing [26c4be2ebe] to disable fast_deletes when m2m_changed signals are connected on top of [https://github.com/django/django/pull/6579].
    22
    3 One question is if `model._meta.auto_created` is indeed a determiner for if a model is a generated m2m through model--I'm assuming it's already being used as such to skip pre/post_delete signals.
    4 
    53There is a design question I think whether the `m2m_changed` signal should only be triggered explicitly via methods on ManyRelatedManager, or any changes to the autogenerated m2m model should in fact be captured. I think there's precedent with deletes at least, in that cascading deletes trigger pre/post_delete signals. So it's not a far stretch that deleted m2m relations trigger m2m_changed signals.
Back to Top