After calling Create/Updates api, it can't find the latest data in db with update_at time or create_at time #288
Conversation
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
AWaterColorPen
changed the title
|
This pull request has been automatically marked as stale because it has not been commented on for at least 7 days, if you encounter a bug in GORM, please report it at https://github.com/go-gorm/gorm/issues with the pull request's link |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Explain your user case and expected results
For example: when we call updates method,
user.update_atis"2021-02-26 20:47:16.823720459Z".But the
UPDATEsql uses"update_at"="2021-02-26 20:47:16.824Z", andSELECTsql uses"update_at"="2021-02-26 20:47:16.823Z"update_atis not consistent.I think
update_atshould be consistent. And it should be no error for this case