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-03-21 UTC."],[[["This webpage provides documentation for the `TransactionMode` enum within the `Google.Cloud.Spanner.Data` namespace, detailing its use in Google Cloud Spanner."],["The latest version documented is `5.0.0-beta05`, with a list of other past versions available, beginning with `3.5.0`."],["The `TransactionMode` enum defines two transaction types: `ReadOnly`, which offers read consistency without write capability, and `ReadWrite`, which supports data writing but may require retries due to potential aborts."],["The listed versions are part of the Google.Cloud.Spanner.Data package, which is located in the Google.Cloud.Spanner[Data] namespace, in the Google.Cloud and Google namespace."]]],[]]
