spanner-jdbc: Step 07 - DirectExecuteResultSet #5815
Merged
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.
The default Cloud Spanner
ResultSetimplementation defers the execution of a query to the first call toResultSet#next(). The JDBC Driver requires that queries are executed directly when a statement is passed to the driver, and that any query errors are returned directly. TheDirectExecuteResultSetis a wrapper around a normal result set that ensures that the query is executed directly, and that any query errors are propagated directly when the result set is created, instead of deferring this until the first call toResultSet#next().