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 available is 5.0.0-beta05, while the current version of this documentation is 3.5.0.\u003c/p\u003e\n"],["\u003cp\u003eThis page provides documentation for the \u003ccode\u003eTransactionMode\u003c/code\u003e enum within the \u003ccode\u003eGoogle.Cloud.Spanner.Data\u003c/code\u003e namespace.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eTransactionMode\u003c/code\u003e enum has two fields: \u003ccode\u003eReadOnly\u003c/code\u003e, which ensures consistency across multiple reads but does not allow writes, and \u003ccode\u003eReadWrite\u003c/code\u003e, which permits writing to Cloud Spanner but may require retries due to potential aborts.\u003c/p\u003e\n"],["\u003cp\u003eThe versions range from 3.5.0 to 5.0.0-beta05.\u003c/p\u003e\n"]]],[],null,[]]
