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

VALUES was incorrectly treated as a function #64

Merged
merged 1 commit into from
Apr 23, 2012

Conversation

bittrance
Copy link

In the version of sqlparse in debian, (INSERT...) VALUES was treated as a function. Then I broke it somehow with my changes to the lexer so it was grouped with table name: <Identifier 'test V...' at 0xb732982c>.

This fix is probably not ideal to solve the issue, but I wanted to submit a fix of some sort as I broke it.

andialbrecht added a commit that referenced this pull request Apr 23, 2012
VALUES was incorrectly treated as a function
@andialbrecht andialbrecht merged commit 843ec03 into andialbrecht:master Apr 23, 2012
@andialbrecht
Copy link
Owner

Thanks! I'll add a comment pointing to this pull request since it seems to be an issue with the parsing/grouping order. I'd expected that the "VALUES" keyword listed in keywords.py solves this issue, but obviously it didn't. :)

ovr pushed a commit to cube-js/sqlparse that referenced this pull request Dec 26, 2020
Implement COLLATE, optional column list in CTEs, and more
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

Successfully merging this pull request may close these issues.

2 participants