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-02 UTC."],[[["This page details the `SingleUseOptions` class for Cloud Spanner's C++ client library, focusing on read-only transactions where Spanner manages the read timestamp."],["The `SingleUseOptions` allow for non-blocking reads, but are limited to a single read operation with functions like `Client::Read()` and `Client::ExecuteQuery()`."],["`SingleUseOptions` cannot be used to create an application-level `Transaction`, but are used for selecting options for a \"single-use\" transaction."],["The provided versions cover a range of releases from 2.11.0 to the release candidate 2.37.0, offering various options for the `SingleUseOptions` class."],["The class `SingleUseOptions` offers constructors for `ReadOnlyOptions`, `Timestamp`, and `std::chrono::nanoseconds`, for flexibility when configuring the read transaction."]]],[]]
