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-03-21 UTC."],[[["The latest version available is 2.37.0-rc, with numerous other versions from 2.36.0 to 2.11.0 also accessible via links."],["This document provides information on the `SingleUseOptions` class, which facilitates read-only transactions in Spanner where Spanner determines the read timestamp within user-defined bounds."],["`SingleUseOptions` allows for non-blocking reads but is restricted to use with a single read operation, either via `Client::Read()` or `Client::ExecuteQuery()`."],["`SingleUseOptions` cannot be utilized to build an application-level `Transaction`, and is designed for single-use, read only operations."],["The `SingleUseOptions` class can be constructed with `ReadOnlyOptions`, `Timestamp`, or `std::chrono::nanoseconds` as parameters, each serving different purposes in setting read options."]]],[]]
