-
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
ddl: fix index length calculation (#13727) #13779
Conversation
/run-all-tests |
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, please fix integration-test
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
please fix common-test |
/run-common-test -tidb-test=pr/958 |
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
/run-all-tests |
@sre-bot merge failed. |
failed. |
/run-common-test -tidb-test=pr/958 |
Please resolve the conflicts @tangenta |
1 similar comment
Please resolve the conflicts @tangenta |
42a2631
to
a1a4ffd
Compare
This PR should be merge together with pingcap/tidb-test#958 |
/run-common-test -tidb-test=pr/958 |
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 |
/run-all-tests |
@sre-bot merge failed. |
/run-common-test -tidb-test=pr/958 |
cherry-pick #13727 to release-3.0
What problem does this PR solve?
In MySQL 8.0:
In TiDB master:
The default charset is
utf8mb4
with at most 4 bytes per character. However, TiDB assumes 1 byte per character by default, which is incorrect.What is changed and how it works?
getIndexColumnLength
, taking charsets into consideration.Check List
Tests
Code changes
N/A
Side effects
Related changes
Release note