Document deterministic connection and statement cleanup - #359
Merged
Merged
Conversation
This was referenced Sep 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The DB and statement docstrings promise cleanup when a function or scope ends. Replace that claim with the actual finalizer behavior and existing explicit close methods. Add a tested
try/finallyexample and explain registered statement cleanup and connection ownership.Related to #344. This documentation change does not diagnose the issue's separate report of missing writes from parallel processes.
Validation: 29 lifecycle checks pass on Julia 1.9.4 and 1.12.7; the new doctest and documentation build pass. Runtime code is unchanged.
Co-authored by Codex