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 document details the `SingleUseOptions` class for Spanner transactions, with a focus on read-only operations."],["It outlines the available versions, ranging from 2.11.0 to 2.37.0-rc, with the latter being the latest release candidate."],["`SingleUseOptions` are for read-only transactions where Spanner automatically determines the read timestamp, which can include user-provided bounds."],["These transactions are limited to a single read operation and cannot be used for constructing application-level transactions, only with functions such as `Client::Read()` and `Client::ExecuteQuery()`."],["Constructors for `SingleUseOptions` are defined using `ReadOnlyOptions`, `Timestamp`, and `std::chrono::nanoseconds`, offering flexibility for different read consistency requirements."]]],[]]
