Changes between Version 2 and Version 3 of Ticket #35890, comment 6
- Timestamp:
- Nov 13, 2024, 9:21:11 AM (2 days ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #35890, comment 6
v2 v3 6 6 In your particular case, `Child.save(update_fields={...})`, won't update `"modified_at"` unless it's specified explicitly so your expectations are already broken for any direct or indirect (through third-party apps) usage of `save(update_fields)`; `update_or_create` is only a single instance of that. 7 7 8 The changes made to handle local concrete fields in #32095 ([https://github.com/django/django/pull/13526 original PR by Florian], [https://github.com/django/django/pull/16072 eventually merged changes by Sarah]) unfortunately didn't cover this use case as [https://github.com/django/django/pull/13526#discussion_r503304956 it wasn't pointed out clearly enough as a point of ambiguity] .8 The changes made to handle local concrete fields in #32095 ([https://github.com/django/django/pull/13526 original PR by Florian], [https://github.com/django/django/pull/16072 eventually merged changes by Sarah]) unfortunately didn't cover this use case as [https://github.com/django/django/pull/13526#discussion_r503304956 it wasn't pointed out clearly enough as a point of ambiguity] and none of the test models made use of MTI. 9 9 10 10 > Why do you think it should be that way?