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 version 4.6.0 currently being documented as well."],["This documentation outlines the `TransactionMode` enum, which is found within the Google.Cloud.Spanner.Data namespace and the Google.Cloud.Spanner.Data.dll assembly."],["The `TransactionMode` enum specifies the transaction mode within the Google Cloud Spanner environment."],["There are two transaction types defined within `TransactionMode`: `ReadOnly` for consistent reads without writes and `ReadWrite` for writing data with pessimistic locking."],["There are multiple previous versions available, from version 3.5.0 up to 4.5.0, and also including the 5.0.0-beta04 pre-release."]]],[]]
