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."],[[["This webpage details the `TransactionMode` enum within the `Google.Cloud.Spanner.Data` library, specifically version 3.6.0 and other versions up to 5.0.0-beta05."],["The `TransactionMode` enum defines two primary modes: `ReadOnly`, which ensures consistency for multiple reads without writes, and `ReadWrite`, which enables writing data through locking and potential two-phase commit."],["The documentation covers a range of versions for the library, from 3.5.0 to the latest beta version 5.0.0-beta05, with links provided for each version's documentation."],["The `ReadOnly` transaction mode does not require committing or locking, and supports reading data at past timestamps, while the `ReadWrite` mode utilizes pessimistic locking and may require retries due to potential aborts."]]],[]]
