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

planner: Point get plan will cause wrong result set #21204

Closed
crazycs520 opened this issue Nov 23, 2020 · 1 comment · Fixed by #21124
Closed

planner: Point get plan will cause wrong result set #21204

crazycs520 opened this issue Nov 23, 2020 · 1 comment · Fixed by #21124
Labels
severity/critical sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Milestone

Comments

@crazycs520
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Related issue: #21123

create table t (id bit(64) primary key);
insert into t values (48);

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

test> select * from t where id in ('0');
+----+
| id |
+----+
0 rows in set

3. What did you see instead (Required)

test> select * from t where id  in ('0');
+----------+
| id       |
+----------+
| 0 |
+----------+
1 row in set. 

4. What is your TiDB version? (Required)

test> select tidb_version();
+-------------------------------------------------------------------+
| tidb_version()                                                    |
+-------------------------------------------------------------------+
| Release Version: v4.0.0-beta.2-1609-gb085cad80                    |
| Edition: Community                                                |
| Git Commit Hash: b085cad80c3196beb470718d38594a161be3bae8         |
| Git Branch: master                                                |
| UTC Build Time: 2020-11-23 06:53:25                               |
| GoVersion: go1.14.4                                               |
| Race Enabled: false                                               |
| TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306 |
| Check Table Before Drop: false                                    |
+-------------------------------------------------------------------
@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 sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants