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 numerous previous versions available for reference, dating back to 3.5.0."],["The `DisposeBehavior` enum defines how `SpannerTransaction` handles resource management when `Dispose` is invoked."],["`DisposeBehavior` has three fields, `CloseResources`, `Detach`, and `ReleaseToPool`, each with distinct actions regarding resource allocation and release upon disposal."],["The `CloseResources` field will automatically close the resources when `Dispose` is called, while the `Detach` field will leave the resources still allocated."],["The `ReleaseToPool` field returns transactional resources to the global pool upon `Dispose` call, however it is invalid for shared transactions."]]],[]]
