Options for "single-use", ReadOnly transactions, where Spanner chooses the read timestamp, subject to user-provided bounds.
This allows reading without blocking.
Because selection of the timestamp requires knowledge of which rows will be read, a single-use transaction can only be used with one read. See Client::Read() and Client::ExecuteQuery(). SingleUseOptions cannot be used to construct an application-level Transaction.
[[["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-04-09 UTC."],[[["This document outlines the `SingleUseOptions` for read-only transactions in Google Cloud Spanner, detailing how Spanner selects the read timestamp within user-specified bounds."],["`SingleUseOptions` are applicable exclusively to single read operations, such as `Client::Read()` and `Client::ExecuteQuery()`, and they are not designed for building application-level transactions."],["The latest version is `2.37.0-rc`, while `2.27.0` is the current version detailed, with documentation available for previous versions going back to `2.11.0`."],["There are 3 constructors detailed for `SingleUseOptions`; `SingleUseOptions(ReadOnlyOptions)`, `SingleUseOptions(Timestamp)`, and `SingleUseOptions(std::chrono::nanoseconds)`."]]],[]]
