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."],[[["Version 3.8.0 of the documentation for `Google.Cloud.Spanner.Data.TransactionMode` is available, with links to various other versions ranging from 3.5.0 up to 5.0.0-beta05."],["`TransactionMode` is an enum that defines the operational modes for transactions, as part of the `Google.Cloud.Spanner.Data` namespace."],["The two available modes are `ReadOnly`, which allows consistent reads but no writes and does not require committing, and `ReadWrite`, which allows writing but may require retries due to potential aborts and uses pessimistic locking."]]],[]]
