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 page provides documentation for `SingleUseOptions` within the Google Cloud Spanner C++ client library, offering various versions ranging from 2.11.0 to the latest release candidate 2.37.0-rc."],["`SingleUseOptions` are used for \"single-use\" and `ReadOnly` transactions, enabling reads without blocking by letting Spanner select the read timestamp within user-defined constraints."],["Due to timestamp selection needing knowledge of the rows being read, single-use transactions are limited to a single read operation, as seen with `Client::Read()` and `Client::ExecuteQuery()`."],["The `SingleUseOptions` class offers constructors accepting `ReadOnlyOptions`, `Timestamp`, or `std::chrono::nanoseconds` for defining transaction behavior."],["`SingleUseOptions` cannot be used to create an application level `Transaction`."]]],[]]
