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-05-02 UTC."],[[["The latest version of the `Google.Cloud.Spanner.Data.TransactionMode` is `5.0.0-beta05`, with previous versions ranging down to `3.5.0`."],["`TransactionMode` is an enum within the `Google.Cloud.Spanner.Data` namespace used to specify the type of transaction."],["The enum has two fields: `ReadOnly`, which allows consistent reads but no writes, and `ReadWrite`, which permits writing data using pessimistic locking and two-phase commit."],["`ReadWrite` transaction may abort, requiring the application to retry."]]],[]]
