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 latest version available is 2.37.0-rc, with the documentation covering versions down to 2.11.0."],["This content details the `SingleUseOptions` for read-only transactions in Spanner, allowing for non-blocking reads where Spanner selects the read timestamp."],["A single-use transaction, as described in the content, is limited to a single read operation and can be used with `Client::Read()` and `Client::ExecuteQuery()`."],["`SingleUseOptions` cannot be utilized to create an application-level `Transaction`."],["`SingleUseOptions` can be created using `ReadOnlyOptions`, `Timestamp`, or `std::chrono::nanoseconds` in the constructor."]]],[]]
