-
Notifications
You must be signed in to change notification settings - Fork 556
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
Misleading error message for typo in IF NOT EXISTS #1169
Comments
Some corner case -
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
👍 makes sense to me -- a nicer error message would indeed be good |
@alamb the challenging part is described in #1169 (comment). Even if we look ahead Keep a backtrace would be the way but it seems too complex for me to working out now ... |
You could potentially special case the error message, perhaps |
I made an attempt at GreptimeDB - GreptimeTeam/greptimedb#3817 If things go well, I'll try to make similar changes to sqlparser-rs. |
See also GreptimeTeam/greptimedb#3471.
For sqlparser-rs -
throws:
IIUC if we found
IF
already, the next keywords SHOULD BENOT EXIST
and thus the parsing logics should be.expect_keywords
.The text was updated successfully, but these errors were encountered: