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 numerous previous versions available for reference, dating back to 3.5.0."],["The provided documentation outlines the `TransactionMode` enum, which controls the behavior of transactions within the Google.Cloud.Spanner.Data library."],["`TransactionMode` supports two modes: `ReadOnly` for consistent reads without writes and `ReadWrite` for transactions that can modify data."],["`ReadOnly` transactions, unlike `ReadWrite` transactions, do not require committing and do not use locks, while `ReadWrite` transactions may abort and require retries."],["This documentation refers to the `Google.Cloud.Spanner.Data.dll` assembly, which is part of the `Google.Cloud.Spanner.Data` namespace."]]],[]]
