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."],[[["The latest version available is 2.37.0-rc, with numerous older versions from 2.36.0 down to 2.11.0 also available for reference."],["`SingleUseOptions` are for \"single-use\" ReadOnly transactions, where Spanner automatically selects the read timestamp based on user-defined boundaries."],["A single-use transaction, limited to one read, can only be used with one `Read()` or `ExecuteQuery()` call."],["`SingleUseOptions` has 3 constructors: one for `ReadOnlyOptions`, one for `Timestamp` and another for `std::chrono::nanoseconds`."],["`SingleUseOptions` are not able to build an application-level `Transaction`."]]],[]]
