Locks for reads within the transaction are not acquired on read.
Instead the locks are acquired on a commit to validate that
read/queried data has not changed since the transaction started.
Pessimistic
Pessimistic lock mode.
Read locks are acquired immediately on read.
Unspecified
Default value.
If the value is not specified, the pessimistic read lock is used.
[[["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-03-21 UTC."],[[["The page provides reference documentation for the `ReadLockMode` enum within the Google Cloud Spanner v1 API, specifically for .NET development."],["The `ReadLockMode` enum is used to determine how read locks are handled in read-write transactions, offering `Optimistic` and `Pessimistic` locking strategies, as well as an `Unspecified` default option."],["The documentation covers a range of versions of the Google.Cloud.Spanner.V1 library, from version 3.5.0 up to the latest beta version 5.0.0-beta05."],["The documentation gives information on the different versions of this api, as well as the different read lock modes available and a description of each."]]],[]]
