-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
server: Revert "server: Improve compatibility with MySQL 5.5 and 5.6 clients … #33142
Conversation
…ingcap#32338)" This reverts commit 7e8ca4c.
[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. |
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
Maybe we need to add more ORM or other connector tests for such scenario... |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 8573e0f
|
Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/e73aef6d2c4bbd368925a2dc3b26bbc3c255b5ca |
…(#32338)"
This reverts commit 7e8ca4c.
What problem does this PR solve?
Issue Number: close #33141
Problem Summary:
Clients cannot connect to TiDB anymore.
What is changed and how it works?
Revert #32338 for now because it's safer.
Check List
Tests
Side effects
Documentation
Release note