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"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThe latest version of the Google.Cloud.Spanner.Data library is 5.0.0-beta05, with a wide range of prior versions available, including 4.2.0.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eTransactionMode\u003c/code\u003e enum within the Google.Cloud.Spanner.Data namespace defines the operational mode of transactions.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eReadOnly\u003c/code\u003e mode transactions ensure consistent data across multiple reads but do not permit any data writes.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eReadWrite\u003c/code\u003e mode transactions are required for writing data and utilize pessimistic locking and two-phase commit processes, which can lead to transaction aborts that require retries.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation and code samples for \u003ccode\u003eTransactionMode\u003c/code\u003e are provided within the Google.Cloud.Spanner.Data.dll assembly.\u003c/p\u003e\n"]]],[],null,[]]
