🐛 Added logic to avoid updating the updated_at field when migrating#9814
Merged
Conversation
no issue - we have to explicitly reset the previous updated_at field, because Bookshelf auto-updates this field on each update - detect `options.migrating`
Contributor
Author
|
@kevinansfield Don't merge it, i am adding a test. |
Contributor
Author
|
@kevinansfield Ready to test :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
no issue
we have to explicitly reset the updated_at field, because Bookshelf auto-updates this field on each update
detect and respect
options.migratingensure
updated_atis set when updating a post in the clientensure
updated_byis set when updating a post in the clientensure
updated_atdoesn't get updated when migratingensure
updated_bydoesn't get updated when migrating