-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Update to sqlparser 0.14 #1796
Update to sqlparser 0.14 #1796
Conversation
FunctionArg::Unnamed(arg) => arg, | ||
}; | ||
|
||
match arg { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needed due to apache/datafusion-sqlparser-rs#378 from @panarch (so we don't allow crazy stuff like SELECT * + * from foo
👍
expr: Box::new(expr), | ||
key: plan_key(key), | ||
} | ||
fn plan_indexed(expr: Expr, mut keys: Vec<SQLExpr>) -> Result<Expr> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had to change this code anyways to handle arbitrary expressions due to apache/datafusion-sqlparser-rs#382 so I took the time to remove the clippy warning too
209b70e
to
dc360f5
Compare
I think it might be nice to update to latest sqlparser before the 7.0.0 release |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I also think it would be better to join 7.0.0
Thanks @xudong963 |
Draft until sqlparser 0.14 is actually releasedWhich issue does this PR close?
Closes #1804
Rationale for this change
A new version of sqlparser is about to be released, and this PR serves as potential QA for this effort
What changes are included in this PR?
Are there any user-facing changes?
New dependency and some new SQL syntax support