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-03-21 UTC."],[[["This page details the `DisposeBehavior` enum within the `Google.Cloud.Spanner.Data` namespace, which defines how `SpannerTransaction` resources are handled when `Dispose` is called."],["The latest version available is `5.0.0-beta05`, but the displayed documentation focuses on version 4.0.0."],["There are three `DisposeBehavior` options: `CloseResources`, which automatically closes resources; `Detach`, which leaves resources allocated; and `ReleaseToPool`, which returns resources to a global pool."],["The `ReleaseToPool` option is invalid for shared transactions, and `Detach` requires at least one instance set to `CloseResources` to prevent resource leaks during parallel reads."]]],[]]