-
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
Character set name is case sensitive in TiDB #8304
Comments
export json : convert("[{"airline_code":"5569","airline_name":"首都航空","airport_from":"HFE","airport_to":"HET","dt_flight":"20108","passenger_idcard":"3412241985********","passenger_idcard_type":"0","passenger_name":"张**","passenger_phone":"1315*"}]" using UTF8MB4) I look at the UFT8MB4 of the default character set from the document.but.When using loader imports , It suggests that UTF8MB4 is not supported. I can change it to UTF8,. This is a bug? |
PTAL @winkyao |
Showing simplified testcase:
Then in TiDB:
|
export json : convert("[{"airline_code":"5569","airline_name":"首都航空","airport_from":"HFE","airport_to":"HET","dt_flight":"20108","passenger_idcard":"3412241985**","passenger_idcard_type":"0","passenger_name":"张**","passenger_phone":"1315*"}]" using UTF8MB4) I look at the UFT8MB4 of the default character set from the document.but.When using loader imports , It |
What't the error message of TiDB and the loader in the log? @evancao77 |
@evancao77 The root cause of this is TiDB not change collation to lower case to compare. I will fix it soon. |
@morgo Below case can pass
|
Bug Report
Please answer these questions before submitting your issue. Thanks!
I use mydumper from version 1. 0 dumper to version 2. 0. 8.for example, character sets are case-sensitive.
What did you expect to see?
I can loader to 2.0.8
What did you see instead?
dumper sql:
create table test
(id int)
ENGINE=InnoDB DEFAULT CHARSET=UTF8 COLLATE=UTF8_BIN;
Can't recognize UTF8, if I change to utf8, it can be created
Is there a parameter that can be controlled case-sensitive
tidb-server -V
or runselect tidb_version();
on TiDB)?1.0.8 to 2.0.8
The text was updated successfully, but these errors were encountered: