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"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThe 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.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eDisposeBehavior\u003c/code\u003e enum defines how \u003ccode\u003eSpannerTransaction\u003c/code\u003e handles resource management when \u003ccode\u003eDispose\u003c/code\u003e is invoked.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eDisposeBehavior\u003c/code\u003e has three fields, \u003ccode\u003eCloseResources\u003c/code\u003e, \u003ccode\u003eDetach\u003c/code\u003e, and \u003ccode\u003eReleaseToPool\u003c/code\u003e, each with distinct actions regarding resource allocation and release upon disposal.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eCloseResources\u003c/code\u003e field will automatically close the resources when \u003ccode\u003eDispose\u003c/code\u003e is called, while the \u003ccode\u003eDetach\u003c/code\u003e field will leave the resources still allocated.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eReleaseToPool\u003c/code\u003e field returns transactional resources to the global pool upon \u003ccode\u003eDispose\u003c/code\u003e call, however it is invalid for shared transactions.\u003c/p\u003e\n"]]],[],null,[]]
