Detaches from the transaction and leaves resources still allocated. You must set
DisposeBehavior to CloseResources on at least one
instance to ensure there are no resource leaks when doing parallel reads.
[[["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-04-09 UTC."],[[["The `DisposeBehavior` enum defines how `SpannerTransaction` handles resource management upon disposal."],["The `CloseResources` option automatically closes resources when `Dispose(Boolean)` is called on a `SpannerTransaction`."],["The `Detach` option only detaches from the transaction, leaving resources allocated, requiring the use of `CloseResources` on at least one instance to avoid leaks during parallel reads."],["The `ReleaseToPool` option returns resources to the global pool upon disposal but is not valid for shared transactions."],["The page content covers multiple versions of the documentation, and as of the latest, the most recent version is 5.0.0-beta05, with a total of 20 versions listed."]]],[]]
