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

FORCE INDEX is not parsed correctly #497

Open
BackEndTea opened this issue Aug 14, 2023 · 0 comments
Open

FORCE INDEX is not parsed correctly #497

BackEndTea opened this issue Aug 14, 2023 · 0 comments
Labels
bug kind/support A request for adding support

Comments

@BackEndTea
Copy link
Contributor

This first query results in the following errors when linting, while the second one has no problems

#1: Unexpected token. (near "=" at position 58)
#2: Unexpected token. (near "uno" at position 60)
#3: Unexpected token. (near "." at position 63)
#4: Unexpected token. (near "id" at position 64)
SELECT *
FROM uno
JOIN dos FORCE INDEX (two_id) ON dos.id = uno.id
SELECT *
FROM uno
JOIN dos  ON dos.id = uno.id
@BackEndTea BackEndTea changed the title FORCE INDEX is not parsed FORCE INDEX is not parsed correctly Aug 14, 2023
@williamdes williamdes added bug kind/support A request for adding support labels Aug 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug kind/support A request for adding support
Projects
None yet
Development

No branches or pull requests

2 participants