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 of the Google.Cloud.Spanner.Data library is 5.0.0-beta05, with a wide range of prior versions available, including 4.2.0."],["The `TransactionMode` enum within the Google.Cloud.Spanner.Data namespace defines the operational mode of transactions."],["`ReadOnly` mode transactions ensure consistent data across multiple reads but do not permit any data writes."],["`ReadWrite` mode transactions are required for writing data and utilize pessimistic locking and two-phase commit processes, which can lead to transaction aborts that require retries."],["The documentation and code samples for `TransactionMode` are provided within the Google.Cloud.Spanner.Data.dll assembly."]]],[]]
