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

some sql stmt was parsed to wrong identifier #21677

Closed
xiongjiwei opened this issue Dec 11, 2020 · 5 comments · Fixed by #21908
Closed

some sql stmt was parsed to wrong identifier #21677

xiongjiwei opened this issue Dec 11, 2020 · 5 comments · Fixed by #21908
Assignees
Labels
component/parser severity/major type/bug The issue is confirmed as a bug.

Comments

@xiongjiwei
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

use test;
create table t(1e int);
insert into t values (1);
select t.1e from test.t;

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

mysql> select t.1e from test.t;
+------+
| 1e   |
+------+
|    1 |
+------+
1 row in set (0.00 sec)

3. What did you see instead (Required)

mysql> select t.1e from test.t;
ERROR 1054 (42S22): Unknown column 't' in 'field list'

4. What is your TiDB version? (Required)

@xiongjiwei xiongjiwei added the type/bug The issue is confirmed as a bug. label Dec 11, 2020
@lzmhhh123 lzmhhh123 added sig/planner SIG: Planner and removed sig/execution SIG execution labels Dec 14, 2020
@lzmhhh123
Copy link
Contributor

/assign @xuyifangreeneyes

@xiongjiwei
Copy link
Contributor Author

similar to pingcap/parser#1114

@xiongjiwei
Copy link
Contributor Author

it's about parser

@XuHuaiyu XuHuaiyu added component/parser and removed sig/planner SIG: Planner labels Dec 14, 2020
@xiongjiwei xiongjiwei changed the title some sql stmt parse wrong identifier some sql stmt was parsed to wrong identifier Dec 17, 2020
@xiongjiwei xiongjiwei changed the title some sql stmt was parsed to wrong identifier some sql stmt was parsed with wrong identifier Dec 17, 2020
@xiongjiwei xiongjiwei changed the title some sql stmt was parsed with wrong identifier some sql stmt was parsed to wrong identifier Dec 17, 2020
@xiongjiwei
Copy link
Contributor Author

/assign @xiongjiwei

@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
component/parser severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants