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 page details the `SingleUseOptions` for Cloud Spanner transactions, specifically within the C++ library, offering a range of versions from 2.11.0 up to the latest release candidate 2.37.0-rc."],["`SingleUseOptions` facilitates read-only transactions where Spanner determines the read timestamp based on user-defined boundaries, allowing for non-blocking reads."],["These single-use transactions are applicable for single read operations, usable with `Client::Read()` and `Client::ExecuteQuery()`, and are not meant for creating application-level transactions."],["The class `SingleUseOptions` can be constructed with `ReadOnlyOptions`, `Timestamp` or `std::chrono::nanoseconds`, each offering a different way to define read parameters."]]],[]]
