tickets: 21461
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 21461 | 2013-11-18 19:38:53 | 2021-06-01 21:41:45 | 2022-03-06 04:16:33.394997 | Accepted | assigned | Database layer (models, ORM) | New feature | Normal | dev | Add pre_update and post_update signals | Quoting Anssi from the ML post https://groups.google.com/forum/#!msg/django-developers/tCzFMpBm5-c/XLHFY0awVJ8J: The idea is that pre_update listeners get a queryset that isn't executed. Accessing that queryset might be costly, but if it isn't accessed, there isn't much cost of adding a pre_update signals. For post_update the signal handler would be given a list of PK values (the original queryset doesn't work for post_update, the update might cause different instances to be returned than was updated, consider qs.filter(deleted=False).update(deleted=True)) This feature will also provide an upgrade path for #21169 (for FK RelatedManager.remove() more specifically). | loic84 | loic84 | 0 | 1 | 1 | 0 | 0 | 0 |