Read-only transactions provide guaranteed consistency across several reads,
but do not allow writes. Read-only transactions can be configured to read at
timestamps in the past. Read-only transactions do not need to be committed and
do not take locks.
ReadWrite
Locking read-write transactions are the only transaction type that support writing
data into Cloud Spanner. These transactions rely on pessimistic locking and, if
necessary, two-phase commit. Locking read-write transactions may abort, requiring
the application to retry.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-09 UTC."],[[["The webpage provides documentation for the `TransactionMode` enum within the `Google.Cloud.Spanner.Data` namespace, specifically showcasing various versions of the Google Cloud Spanner Data library."],["The latest beta version of the library documented is `5.0.0-beta05`, while the most recent stable release documented is `4.6.0`, alongside many older versions going as far back as `3.5.0`."],["The `TransactionMode` enum has two fields: `ReadOnly`, which supports consistent reads but not writes and `ReadWrite`, which supports writing data into Cloud Spanner but may abort and require retries."],["Version `4.1.0` of the Google.Cloud.Spanner.Data library is listed, with links provided for all other versions from `3.5.0` up to `5.0.0-beta05`, to view their relevant documentation."]]],[]]
