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."],[[["This 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 during read-write transactions in Google Cloud Spanner."],["The latest version documented is `5.0.0-beta05`, and the documentation includes many older versions as far back as version `3.5.0` for the `ReadLockMode` enum."],["The enum has three possible values: `Optimistic`, `Pessimistic`, and `Unspecified`, each controlling the timing and behavior of lock acquisition during transactions."],["`Pessimistic` locking acquires locks immediately on read, `Optimistic` locking acquires locks upon commit, and `Unspecified` defaults to pessimistic locking."]]],[]]
