-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
chore(deps): update sqlparser requirement from 0.35 to 0.36.1 #7051
Conversation
Updates the requirements on [sqlparser](https://github.com/sqlparser-rs/sqlparser-rs) to permit the latest version. - [Changelog](https://github.com/sqlparser-rs/sqlparser-rs/blob/main/CHANGELOG.md) - [Commits](apache/datafusion-sqlparser-rs@v0.35.0...v0.35.0) --- updated-dependencies: - dependency-name: sqlparser dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
CI fails, I think you need to update the lock file for the CLI. |
@@ -2175,13 +2175,13 @@ mod tests { | |||
async fn create_variable_err() -> Result<()> { | |||
let ctx = SessionContext::new(); | |||
|
|||
let err = plan_and_collect(&ctx, "SElECT @= X#=?!~ 5") |
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.
without chis change, sqlparser complains (reasonably) about X#=?!~ 5
not being a valid identifier.
https://github.com/apache/arrow-datafusion/actions/runs/5621460600/job/15232281958?pr=7051
---- execution::context::tests::create_variable_err stdout ----
thread 'execution::context::tests::create_variable_err' panicked at 'assertion failed: `(left == right)`
left: `"SQL error: ParserError(\"Expected end of statement, found: =\")"`,
right: `"Error during planning: variable [\"@\"] has no type information"`', datafusion/core/src/execution/context.rs:2182:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
So I changed the test to preserver the error (rather than updating the error to be a parse error)
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.
Make sense to me❤️
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.
Thanks @alamb
Merge it quickly because of it may accumulate some conflict. |
Which issue does this PR close?
Closes #7037
Rationale for this change
Keep up with dependencies
What changes are included in this PR?
See title
Are these changes tested?
Yes, existing CI
Are there any user-facing changes?