Support non-prepared queries execution#555
Merged
staticlibs merged 1 commit intoduckdb:mainfrom Feb 8, 2026
Merged
Conversation
staticlibs
force-pushed
the
execute_direct
branch
from
a1857a8 to
b18a7b9
Compare
Currently JDBC driver always uses prepare+execute even if the client calls `Statement#executeQuery()`, not the `Connection#prepareStatement()` along with `PreparedStatement#executeQuery()`. This can cause problems (side effects) like the one in duckdb#467. With this PR native prepared statement is only used when Java `PreparedStatement` is used. Pending query execution logic is used otherwise. Testing: tests added to cover concurrent closure for prepared and non-prepared statements separately. Ref: duckdblabs/duckdb-internal#6682
staticlibs
force-pushed
the
execute_direct
branch
from
b18a7b9 to
1bbabe3
Compare
staticlibs
added a commit
to staticlibs/duckdb-java
that referenced
this pull request
Feb 8, 2026
This is a backport of the PR duckdb#555 to `v1.5-variegata` stable branch. Currently JDBC driver always uses prepare+execute even if the client calls `Statement#executeQuery()`, not the `Connection#prepareStatement()` along with `PreparedStatement#executeQuery()`. This can cause problems (side effects) like the one in duckdb#467. With this PR native prepared statement is only used when Java `PreparedStatement` is used. Pending query execution logic is used otherwise. Testing: tests added to cover concurrent closure for prepared and non-prepared statements separately. Ref: duckdblabs/duckdb-internal#6682
staticlibs
added a commit
that referenced
this pull request
Feb 8, 2026
This is a backport of the PR #555 to `v1.5-variegata` stable branch. Currently JDBC driver always uses prepare+execute even if the client calls `Statement#executeQuery()`, not the `Connection#prepareStatement()` along with `PreparedStatement#executeQuery()`. This can cause problems (side effects) like the one in #467. With this PR native prepared statement is only used when Java `PreparedStatement` is used. Pending query execution logic is used otherwise. Testing: tests added to cover concurrent closure for prepared and non-prepared statements separately. Ref: duckdblabs/duckdb-internal#6682
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently JDBC driver always uses prepare+execute even if the client calls
Statement#executeQuery(), not theConnection#prepareStatement()along withPreparedStatement#executeQuery().This can cause problems (side effects) like the one in #467.
With this PR native prepared statement is only used when Java
PreparedStatementis used. Pending query execution logic is used otherwise.Testing: tests added to cover concurrent closure for prepared and non-prepared statements separately.
Ref: duckdblabs/duckdb-internal#6682