PreparedStatement.executeQuery does not mark the result set as requested #107
Copy link
Copy link
Closed
Labels
P2Normal priority: edge case, feature gap, or test/process improvementNormal priority: edge case, feature gap, or test/process improvementbugSomething isn't workingSomething isn't working
Description
LibsqlPreparedStatement.executeQuery calls assignResultSet(resultSet, false). LibsqlStatement.executeQuery passes true, which is the contract from #85.
With a prepared statement, ps.executeQuery(); ps.getResultSet() returns the same open result set. sqlite-jdbc throws because JDBC3PreparedStatement.executeQuery ends in getResultSet(), so a second request fails.
LibsqlStatementLifecycleTest covers only the plain Statement.
Expected:
- Pass
truein the prepared path. - Add the prepared statement case to the lifecycle tests.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P2Normal priority: edge case, feature gap, or test/process improvementNormal priority: edge case, feature gap, or test/process improvementbugSomething isn't workingSomething isn't working
Activity
fix(jdbc): mark prepared executeQuery result set as requested (#139)