Ensure mtime
update is triggered for Django
#2935
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #2934
The
ModelWrapper
utility class ensures that a database model instanceis automatically saved if a model field is updated and the instance is
already stored. This prevents the implementation from having to call
save
manually every time a field is updated. The Django implementationuses the
update_fields
keyword of thesave
method, to update onlythe field affected. However, this circumvents the
auto_now
of themtime
field. This bug is currently not visible, because in the modelwrapper currently also always updates the node version after a model
field is updated of a stored instance. This, however, uses a normal
save
and so does properly update themtime
. Once this updating ofthe node version would have been removed, this bug will be revealed.