feat: trace sharding log #29
Open
+48
−2
Conversation
This file contains 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
|
Affects |
|
related to go-gorm/gorm#5304 |
|
It fixed in next gorm version |
|
Hello @a631807682 Can you fix the file conflict? Thank you. |
hyperphoton
requested review from
hyperphoton
and removed request for
hyperphoton and
jinzhu
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What did this pull request do?
Even if we use the sharding model, the log will only print the original sql.
This feature is used to print the sql log of the actual execution.
This is similar to
LastQuery, the difference is that in a model with an associated relationship, the log will be printed multiple times, whileLastQueryrecords the last time.User Case Description