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

Make TiDB accept 'AND NO CHAIN NO RELEASE' in SQL syntax #649

Closed
YouhuaLi opened this issue Nov 25, 2019 · 4 comments · Fixed by #751
Closed

Make TiDB accept 'AND NO CHAIN NO RELEASE' in SQL syntax #649

YouhuaLi opened this issue Nov 25, 2019 · 4 comments · Fixed by #751

Comments

@YouhuaLi
Copy link

YouhuaLi commented Nov 25, 2019

Feature Request

Is your feature request related to a problem? Please describe:

When I test my current application with TiDB, I got a lot of errors as:

'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 12 near \"AND NO CHAIN NO RELEASE\" ')]"

Describe the feature you'd like:

Make TiDB accept 'AND NO CHAIN NO RELEASE' as valid SQL syntax, by even do nothing and ignore that.

Describe alternatives you've considered:

I can change my existing software code to remove those codes, but that will be a lot of efforts and break online migraiton process.

Teachability, Documentation, Adoption, Migration Strategy:

@YouhuaLi YouhuaLi changed the title Make TiDB accept 'AND NO CHAIN NO RELEASE' in SQL sytanx Make TiDB accept 'AND NO CHAIN NO RELEASE' in SQL syntax Nov 25, 2019
@shenli
Copy link
Member

shenli commented Nov 26, 2019

@YouhuaLi Could you show use the whole statement? Thanks!

@shenli
Copy link
Member

shenli commented Nov 26, 2019

@YouhuaLi
Copy link
Author

they are just:

COMMIT AND NO CHAIN NO RELEASE
ROLLBACK AND NO CHAIN NO RELEASE

@dasinlsb
Copy link
Contributor

dasinlsb commented Feb 27, 2020

let me try it, just accept the syntax and do nothing :|

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

Successfully merging a pull request may close this issue.

4 participants