Dandandan opened a new pull request, #22204: URL: https://github.com/apache/datafusion/pull/22204
## Which issue does this PR close? - Closes #22197. ## Rationale for this change `EXEC()` and `EXECUTE()` can parse as `Statement::Execute` without a statement name. The planner previously unwrapped that optional name and panicked on user-supplied SQL. ## What changes are included in this PR? - Return a planning error when `EXECUTE` has no statement name. - Add sqllogictest coverage for the malformed `EXEC` / `EXECUTE` forms from the issue. ## Are these changes tested? - `cargo test -p datafusion-sqllogictest --test sqllogictests -- prepare` - `cargo fmt --all` - `cargo clippy --all-targets --all-features -- -D warnings` ## Are there any user-facing changes? Malformed `EXEC` / `EXECUTE` statements without a name now return a planning error instead of panicking. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
