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 provides documentation for the `DisposeBehavior` enum within the `Google.Cloud.Spanner.Data` namespace, detailing how `SpannerTransaction` handles resource disposal."],["The latest version documented is `5.0.0-beta05`, with a history of previous versions also available, dating back to `3.5.0`."],["The `DisposeBehavior` enum defines three distinct behaviors: `CloseResources`, which automatically closes resources upon disposal; `Detach`, which detaches from the transaction but keeps resources allocated; and `ReleaseToPool`, which returns resources to a global pool."],["`ReleaseToPool` is not a valid option for shared transactions, and `Detach` requires setting `DisposeBehavior` to `CloseResources` on at least one instance to prevent resource leaks during parallel reads."]]],[]]
