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 in the `Google.Cloud.Spanner.Data` namespace defines how a `SpannerTransaction` handles resource management when `Dispose` is called."],["Version 5.0.0-beta05 is the latest beta version available for the Google Cloud Spanner Data library, and the documentation displays versions going back to 3.5.0."],["The `CloseResources` field within `DisposeBehavior` ensures resources are automatically closed when `Dispose(Boolean)` is invoked."],["The `Detach` field in the `DisposeBehavior` enum detaches from the transaction, but requires setting `DisposeBehavior` to `CloseResources` to prevent resource leaks in parallel read scenarios."],["The `ReleaseToPool` field allows transactional resources to be returned to a global pool upon `Dispose(Boolean)`, but it's incompatible with shared transactions."]]],[]]
