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\u003eThis webpage provides documentation for the \u003ccode\u003eTransactionMode\u003c/code\u003e enum within the \u003ccode\u003eGoogle.Cloud.Spanner.Data\u003c/code\u003e namespace, detailing its use in Cloud Spanner transactions.\u003c/p\u003e\n"],["\u003cp\u003eThe latest version of the documentation is for 5.0.0-beta05, with previous versions from 3.5.0 through 5.0.0-beta04 also accessible via the links provided.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eTransactionMode\u003c/code\u003e enum has two possible fields: \u003ccode\u003eReadOnly\u003c/code\u003e, which offers consistent reads without allowing writes, and \u003ccode\u003eReadWrite\u003c/code\u003e, which allows data writes using pessimistic locking.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation includes the assembly information, which is \u003ccode\u003eGoogle.Cloud.Spanner.Data.dll\u003c/code\u003e, as well as providing the name and description of the fields in a table format.\u003c/p\u003e\n"]]],[],null,[]]
