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 document details the `SingleUseOptions` class within the Google Cloud Spanner C++ client library, focusing on read-only transactions where Spanner selects the read timestamp."],["The latest version of `SingleUseOptions` is version 2.37.0-rc, and the document provides links to documentation for multiple versions, ranging from 2.11.0 to the latest."],["`SingleUseOptions` allow for reading without blocking but are limited to a single read operation, usable with `Client::Read()` and `Client::ExecuteQuery()`."],["`SingleUseOptions` can be created using `ReadOnlyOptions`, a `Timestamp` for a minimum read timestamp, or a `std::chrono::nanoseconds` for maximum staleness."],["`SingleUseOptions` is not used to construct an application level `Transaction`, it can only be used for single use read-only transactions."]]],[]]
