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 version 4.6.0 currently being documented as well.\u003c/p\u003e\n"],["\u003cp\u003eThis documentation outlines the \u003ccode\u003eTransactionMode\u003c/code\u003e enum, which is found within the Google.Cloud.Spanner.Data namespace and the Google.Cloud.Spanner.Data.dll assembly.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eTransactionMode\u003c/code\u003e enum specifies the transaction mode within the Google Cloud Spanner environment.\u003c/p\u003e\n"],["\u003cp\u003eThere are two transaction types defined within \u003ccode\u003eTransactionMode\u003c/code\u003e: \u003ccode\u003eReadOnly\u003c/code\u003e for consistent reads without writes and \u003ccode\u003eReadWrite\u003c/code\u003e for writing data with pessimistic locking.\u003c/p\u003e\n"],["\u003cp\u003eThere 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.\u003c/p\u003e\n"]]],[],null,[]]
