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."],[[["The content provides documentation for the `TransactionMode` enum within the `Google.Cloud.Spanner.Data` namespace, specifically showing versioned documentation from version 3.5.0 up to the latest beta, 5.0.0-beta05."],["`TransactionMode` is an enum that specifies the operational mode for a transaction in Cloud Spanner, as detailed within the document."],["The documentation lists two specific modes of operation within `TransactionMode`: `ReadOnly`, which supports consistent reads without writes and does not require commits, and `ReadWrite`, which is the only mode that allows writing to Cloud Spanner, relying on pessimistic locking."],["The documentation is versioned, allowing developers to view details about the `TransactionMode` enum across different releases of `Google.Cloud.Spanner.Data.dll`."],["The latest version of this document is 5.0.0-beta05."]]],[]]
