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."],[[["The page documents the `SingleUseOptions` for Spanner transactions, which are designed for read-only operations where Spanner automatically selects the read timestamp."],["The latest version is `2.37.0-rc`, and the page provides links to documentation for versions ranging from `2.37.0-rc` down to `2.11.0`."],["`SingleUseOptions` are used for reading without blocking, allowing for one read per transaction via `Client::Read()` or `Client::ExecuteQuery()`."],["`SingleUseOptions` cannot be used to create an application-level `Transaction`, and they are designed for single-use read-only transactions."],["There are three constructors for `SingleUseOptions`, accepting `ReadOnlyOptions`, `Timestamp`, or `std::chrono::nanoseconds` parameters to customize the transaction behavior."]]],[]]
