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 referencing version 3.9.0 and listing versions up to the latest beta release."],["The `TransactionMode` enum defines the operational mode for transactions within Cloud Spanner, encompassing both `ReadOnly` and `ReadWrite` options."],["`ReadOnly` transactions offer consistency across multiple reads without allowing writes and are free from locks or commit processes."],["`ReadWrite` transactions, which are necessary for writing data to Cloud Spanner, use pessimistic locking and may require retry logic due to potential aborts."],["The page provides a comprehensive version history of `Google.Cloud.Spanner.Data`, including links to access documentation for each version, starting from 3.5.0 all the way to the latest beta release (5.0.0-beta05)."]]],[]]
