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 latest version of the Google.Cloud.Spanner.Data library is 5.0.0-beta05, with several previous versions available for reference, going back to 3.5.0."],["The content describes the `DisposeBehavior` enum, which is part of the `Google.Cloud.Spanner.Data` namespace, and is defined in the Google.Cloud.Spanner.Data.dll assembly."],["The `DisposeBehavior` enum dictates how `SpannerTransaction` handles resource disposal when the `Dispose` method is invoked."],["There are three available options for the `DisposeBehavior`: `CloseResources`, `Detach`, and `ReleaseToPool`, each offering a different method for managing resources."],["The `ReleaseToPool` dispose behavior is invalid for shared transactions."]]],[]]