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."],[[["This page details the `SingleUseOptions` class within the Google Cloud Spanner C++ library, providing documentation for various versions."],["The latest release candidate version for `SingleUseOptions` is 2.37.0-rc, with a range of previous versions also documented up to 2.11.0."],["`SingleUseOptions` allows for read-only transactions where Spanner determines the read timestamp within user-defined limits."],["`SingleUseOptions` are designed for single-read operations and are compatible with `Client::Read()` and `Client::ExecuteQuery()`, and cannot construct an application-level `Transaction`."],["Constructors for `SingleUseOptions` are provided that support `ReadOnlyOptions`, `Timestamp`, and `std::chrono::nanoseconds` to define the parameters of the read."]]],[]]
