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."],[[["The page provides documentation for `SingleUseOptions` in the Google Cloud Spanner C++ client library, with version 2.37.0-rc being the latest and 2.11.0 the oldest version listed."],["`SingleUseOptions` are designed for \"single-use,\" ReadOnly transactions where Spanner automatically chooses the read timestamp within the constraints set by the user."],["A single-use transaction is limited to a single read operation, applicable via `Client::Read()` or `Client::ExecuteQuery()`."],["`SingleUseOptions` cannot be used to create an application-level `Transaction`."],["The class can be constructed with `ReadOnlyOptions`, `Timestamp`, or `std::chrono::nanoseconds` to define transaction parameters like timestamp or max staleness."]]],[]]
