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 page details the `SingleUseOptions` for Cloud Spanner transactions, which allow for non-blocking read operations."],["`SingleUseOptions` are limited to a single read operation, either with `Client::Read()` or `Client::ExecuteQuery()`."],["The `SingleUseOptions` cannot be used for constructing application-level `Transaction` objects in Cloud Spanner."],["The `SingleUseOptions` are designed for read-only transactions where Spanner automatically selects the read timestamp, based on user-specified bounds."],["The page provides a list of documentation for this content over a range of versions from 2.11.0 to the latest release candidate 2.37.0-rc."]]],[]]
