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

clustered index + new collation + old row format got wrong result #24541

Closed
lysu opened this issue May 11, 2021 · 1 comment · Fixed by #24544
Closed

clustered index + new collation + old row format got wrong result #24541

lysu opened this issue May 11, 2021 · 1 comment · Fixed by #24544
Labels
severity/critical type/bug The issue is confirmed as a bug.

Comments

@lysu
Copy link
Contributor

lysu commented May 11, 2021

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

start a tidb with the new collation enabled and MUST started with TiKV(because unistore only support new format- -)

set global tidb_row_format_version=1;

reconnect a new session

create table t2(col_1 varchar(132) CHARACTER SET utf8 COLLATE utf8_unicode_ci, primary key(col_1) clustered);
insert into t2 select 'aBc';
select * from t2 where col_1 = 'aBc';

2. What did you expect to see? (Required)

aBc

3. What did you see instead (Required)

mysql> select * from t2 where col_1 = 'aBc';
+--------+
| col_1  |
+--------+
| 3J` |
+--------+
1 row in set (0.01 sec)

4. What is your TiDB version? (Required)

v5.0.1 tidb + tikv

master 5460b5c

@ti-srebot
Copy link
Contributor

Please edit this comment or add a new comment to complete the following information

Not a bug

  1. Remove the 'type/bug' label
  2. Add notes to indicate why it is not a bug

Duplicate bug

  1. Add the 'type/duplicate' label
  2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/critical type/bug The issue is confirmed as a bug.
Projects
None yet
3 participants