spanner-jdbc: Step 20 - ReadOnlyTransaction #5897
Conversation
|
|
||
| @Override | ||
| public ResultSet executeQuery(Statement statement, QueryOption... options) { | ||
| if (readTimestamp == null) { |
There was a problem hiding this comment.
How come we are overriding these methods for the test?
There was a problem hiding this comment.
I guess the naming is a little bit confusing in this case, as we have two different ReadOnlyTransactions in this case. The interface that is being implemented is com.google.cloud.spanner.ReadOnlyTransaction, i.e. the read-only transaction of the normal client library, and not the read-only transaction of the connection API. That is done in this test in order to create a simple mock object with some logic to use in the test cases.
The logic in the executeQuery(...) method is intended to make sure the connection API actually uses the correct staleness mode for the underlying read-only transaction (and to return a mock result set).
Adds
ReadOnlyTransactionfor the internal Spanner connection API. These transactions can only be used to execute queries. ReadOnlyTransactions support using a read-only staleness mode and timestamp or staleness.