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."],[[["This webpage documents various versions of the `TransactionMode` enum within the `Google.Cloud.Spanner.Data` library, ranging from version 3.5.0 up to the latest beta version 5.0.0-beta05."],["The `TransactionMode` enum defines the operational mode for Cloud Spanner transactions, and it currently has two defined states, `ReadOnly` and `ReadWrite`."],["`ReadOnly` transactions provide data consistency across multiple reads, do not permit writes, can be configured for past timestamps, and require no commits or locks."],["`ReadWrite` transactions support writing to Cloud Spanner, utilize pessimistic locking and two-phase commits, and may necessitate application-level retries due to potential aborts."],["The most recent version of the library is `5.0.0-beta05`, however the `3.15.1` version is also referenced as a stable version."]]],[]]
