-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
session: del NO_BACKSLASH_ESCAPES sql mode for internal sql (#43966) #43994
session: del NO_BACKSLASH_ESCAPES sql mode for internal sql (#43966) #43994
Conversation
Signed-off-by: ti-chi-bot <[email protected]>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
Signed-off-by: guo-shaoge <[email protected]>
Signed-off-by: guo-shaoge <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/merge |
This pull request has been accepted and is ready to merge. Commit hash: d7125fa
|
/retest |
/run-unit-test |
This is an automated cherry-pick of #43966
What problem does this PR solve?
Issue Number: close #43392
Problem Summary: As issue said,
NO_BACKSLASH_ESCAPES
may cause internal sql parse failed.What is changed and how it works?
Delete
NO_BACKSLASH_ESCAPES
for internal sql mode.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.