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

filter empty sql to avoid IndexOutOfBoundException #246

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

trung
Copy link

@trung trung commented Jan 4, 2024

resolves #245

Make sure that:

  • You have read the contribution guidelines.
  • You have created a feature request first to discuss your contribution intent. Please reference the feature request ticket number in the pull request.
  • You use the code formatters provided here and have them applied to your changes. Don't submit any formatting related changes.
  • You submit test cases (unit or integration tests) that back your changes.

Signed-off-by: ⚆ Trung Nguyen <[email protected]>
@@ -102,6 +102,7 @@ public Flux<H2Result> execute() {
Assert.requireTrue(!this.bindings.open, "No unfinished bindings!");

return Flux.fromArray(this.sql.split(";"))
.filter(sql -> !sql.trim().isEmpty())
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there is a bigger problem.

split(";") cannot be used to break SQL into separate statements properly. This character may be used in comments, various types of character string literals, and quoted identifiers.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right. If we remove the split, would it there be any serious implication? Mainly backward compatibility IMO.

Or we need to have a more sophisticated split than just string split.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be so great to be able to make use of H2's internal parsing utils instead of us having to make a dance around H2 externally. Too bad, I wasn't able to convince @katzyn to bring this project closer to H2.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we consider this fix as an interim patch while having much more careful changes to deal with ; parsing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

execute empty sql causing IndexOutOfBoundsException
3 participants