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 multiple previous versions available, including the current version 3.14.0, which can be found within the list."],["The content describes the `TransactionMode` enum, which specifies the transaction mode within the `Google.Cloud.Spanner.Data` namespace and its location within the Google.Cloud.Spanner.Data.dll assembly."],["The `TransactionMode` enum includes two fields: `ReadOnly` for read-only transactions that ensure consistency across reads without allowing writes, and `ReadWrite` for transactions that support writing data using pessimistic locking."],["The document shows a range of versions from 3.5.0 all the way to 5.0.0-beta05, offering the user with an extensive history of the library."]]],[]]
