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 latest version available is 5.0.0-beta05, while version 3.10.0 is a currently specified version."],["A range of previous versions are accessible, including those within series 3, 4, and 5."],["The `TransactionMode` enum within the `Google.Cloud.Spanner.Data` namespace specifies how a transaction will function."],["There are two fields for the Transaction Mode, `ReadOnly`, which provides consistency but no writes, and `ReadWrite`, which uses locking to allow writing."],["The ReadWrite transaction mode is the only mode that supports writing data into Cloud Spanner."]]],[]]
