fix: ExplainSQL using consecutive pairs of escaper in SQL string represents an escaper #6766
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
…esents an escaper Preventing it from being interpreted as the string terminator. This is a widely used escape mechanism in SQL standards and is applicable in most relational databases.
|
@jinzhu Please review this PR when you have time. |
iTanken
added a commit
to godoes/gorm-oracle
that referenced
this pull request
Jan 3, 2024
go: upgraded gorm.io/gorm v1.25.5 => v1.25.6-0.20231228115336-87decced23be fix: github.com/go-gorm/gorm/pull/6766 Signed-off-by: liutianqi <[email protected]>
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?
logger.ExplainSQLusing consecutive pairs of escaper in SQL string represents an escaper, preventing it from being interpreted as the string terminator. This is a widely used escape mechanism in SQL standards and is applicable in most relational databases.go-gorm/postgres#236
User Case Description
go-gorm/playground#677