Skip to content
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: update parser to make TiDB treat charset and collate case insensitive #8577

Merged
merged 8 commits into from
Dec 7, 2018
Merged

ddl: update parser to make TiDB treat charset and collate case insensitive #8577

merged 8 commits into from
Dec 7, 2018

Conversation

winkyao
Copy link
Contributor

@winkyao winkyao commented Dec 4, 2018

What problem does this PR solve?

Fix #8304

What is changed and how it works?

Actually, pingcap/parser#66 fix this problem, we just add some test cases and update the go.mod to the corresponding parser will work.

Check List

Tests

  • Unit test

Related changes

  • Need to cherry-pick to the release branch

This change is Reviewable

@winkyao winkyao changed the title ddl: update parser to make TiDB treat charset and collate case insens… ddl: update parser to make TiDB treat charset and collate case insensitive Dec 4, 2018
@winkyao
Copy link
Contributor Author

winkyao commented Dec 4, 2018

@tiancaiamao PTAL

Copy link
Contributor

@zimulala zimulala left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Release Version:  v2.0.9-20-ged6e8ff
Git Commit Hash:  ed6e8ff6b3df1eb64b1050e008d922b981a75329
tidb> create table test(id int) ENGINE=InnoDB DEFAULT CHARSET=UTF8 COLLATE=UTF8_BIN;
ERROR 1115 (42000): Unknown character set: 'UTF8'
tidb> create table test(id int) ENGINE=InnoDB DEFAULT CHARSET=UTF8 COLLATE=utf8_bin;
ERROR 1115 (42000): Unknown character set: 'UTF8'
Release Version: v2.1.0-2-gb2382fb
Git Commit Hash: b2382fbe6c34d2ce200018ff765b1acb05cc7f6b
tidb> create table test(id int) ENGINE=InnoDB DEFAULT CHARSET=UTF8 COLLATE=UTF8_BIN;
ERROR 1115 (42000): Unknown character set: 'UTF8'
tidb> create table test(id int) ENGINE=InnoDB DEFAULT CHARSET=UTF8 COLLATE=utf8_bin;
Query OK, 0 rows affected (0.11 sec)

It seems can't pass these tests in v2.0 and v2.1. We need to fix these.

@tiancaiamao
Copy link
Contributor

@zimulala release-2.1 is not using master branch parser

@tiancaiamao
Copy link
Contributor

/run-all-tests

@winkyao
Copy link
Contributor Author

winkyao commented Dec 5, 2018

@zimulala The changes in parser need to cherry-pick to 2.1 branches later. Never mind.

Copy link
Contributor

@crazycs520 crazycs520 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@crazycs520 crazycs520 added the status/LGT1 Indicates that a PR has LGTM 1. label Dec 6, 2018
@tiancaiamao
Copy link
Contributor

LGTM

@tiancaiamao
Copy link
Contributor

/run-all-tests

@zz-jason zz-jason added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Dec 7, 2018
@you06 you06 added the sig/sql-infra SIG: SQL Infra label Mar 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/sql-infra SIG: SQL Infra status/LGT2 Indicates that a PR has LGTM 2.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Character set name is case sensitive in TiDB
6 participants