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 provides reference information for `SingleUseOptions` within the Google Cloud Spanner C++ library, with version 2.37.0-rc being the latest release."],["`SingleUseOptions` facilitates read-only transactions where Spanner automatically selects the read timestamp, adhering to user-defined boundaries."],["Single-use transactions are designed for a single read operation and can be employed with `Client::Read()` and `Client::ExecuteQuery()` methods."],["`SingleUseOptions` cannot be utilized to create application-level transactions, and the document covers the constructors that define different ways to set up the single use transaction."],["The documentation is available for multiple versions, spanning from version 2.11.0 up to 2.37.0-rc, with all versions having the same class documentation for `SingleUseOptions`."]]],[]]
