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 content details various versions of the `Google.Cloud.Spanner.Data` library, ranging from the latest beta version 5.0.0-beta05 down to version 3.5.0."],["This page specifically documents the `TransactionMode` enum, part of the `Google.Cloud.Spanner.Data` namespace within the `Google.Cloud.Spanner.Data.dll` assembly."],["The `TransactionMode` enum defines two fields: `ReadOnly`, which ensures consistency across multiple reads without writes, and `ReadWrite`, which supports writing data using pessimistic locking and two-phase commits."],["The main versions of this API are 4.x and the older 3.x, with many sub-versions existing for both."]]],[]]
