Implement the new extensible transaction definition in R2DBC SPI #238
Labels
Milestone
Comments
elefeint
changed the title
meltsufin
pushed a commit
that referenced
this issue
Oct 30, 2023
… to support @transactional annotation (#738) Implemented the following classes and methods to conform to R2DBC SPI which enables supporting `@Transactional` annotation in [Spring Data Dialect](https://github.com/GoogleCloudPlatform/spring-cloud-gcp/tree/main/spring-cloud-spanner-spring-data-r2dbc). - `Connection#beginTransaction(TransactionDefinition)` method so that it can be used by a `TransactionManager` when `@Transactional` annotation is used. ✅ - `Connection#getTransactionIsolationLevel` returns SERIALIZABLE as it is the closest level to EXTERNAL_CONSISTENCY which spanner supports. ✅ - `Connection#setTransactionIsolationLevel(IsolationLevel)` accepts only `IsolationLevel.SERIALIZABLE` and throw `UnsupportedOperationException` otherwise. ✅ - Introduced `SpannerTransactionDefinition`, an implementation of `TransactionDefinition`(R2DBC spi) to configure the transaction attributes which will be used by `Connection#beginTransaction(TransactionDefinition)` method. ✅ Fixes: #238.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Extend TransactionDefinition to support read-only, read-write, stale-read (and partitioned DML?) transactions with the extensible transaction definition in r2dbc/r2dbc-spi#159.
The transaction definition should map its own values to valid calls to already-implemented
DatabaseClientTransactionManager.beginReadonlyTransaction(TimestampBound timestampBound)The text was updated successfully, but these errors were encountered: