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

Incompatible for skip locked statements. #940

Open
cncal opened this issue Jul 24, 2020 · 1 comment
Open

Incompatible for skip locked statements. #940

cncal opened this issue Jul 24, 2020 · 1 comment

Comments

@cncal
Copy link
Contributor

cncal commented Jul 24, 2020

Bug Report

  1. What did you do?
mysql> CREATE TABLE t (i INT, PRIMARY KEY (i)) ENGINE = InnoDB;
mysql> INSERT INTO t (i) VALUES(1),(2),(3);
mysql> SELECT * FROM t FOR UPDATE SKIP LOCKED;
  1. What did you expect to see?
+---+
| i |
+---+
| 1 |
+---+
| 2 |
+---+
| 3 |
+---+
  1. What did you see instead?
Error Code: 1064. You have an error in your SQL syntax; check the manual that corresponds to your TiDB version for the right syntax to use line 1 column 31 near "SKIP LOCKED" 
  1. What version of TiDB SQL Parser are you using?

    v0.0.0-20200623082809-b74301ac298b

@ghost
Copy link

ghost commented Jul 26, 2020

The TiDB issue for this is pingcap/tidb#18207

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant