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-14 UTC."],[[["This document outlines the `SingleUseOptions` for read-only transactions in Google Cloud Spanner, detailing how Spanner selects the read timestamp within user-specified bounds."],["The `SingleUseOptions` can only be used for a single read operation, such as with `Client::Read()` or `Client::ExecuteQuery()`."],["`SingleUseOptions` cannot be directly utilized to create an application-level `Transaction` within Spanner."],["The document provides an extensive list of version releases, starting from version `2.11.0` all the way up to the latest release candidate `2.37.0-rc`."],["The class allows for construction using `ReadOnlyOptions`, a specific `Timestamp`, or a `std::chrono::nanoseconds` for `max_staleness`."]]],[]]
