Skip to content

Conversation

@NickCraver
Copy link
Contributor

In cases of background threads or breaks, this was leaving connections open and exhausting the pool. Instead, let Dapper handle it internally (it'll soft open and close as needed internally).

Nick Craver added 2 commits August 19, 2020 16:43
This needs a big refactor, but as a mitigation we can at least try and dispose any CallContext members from the background.
Let Dapper handle it per query instead
Copy link
Contributor

@tarynpratt tarynpratt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@NickCraver NickCraver merged commit df38440 into master Aug 19, 2020
@johnmwright johnmwright deleted the craver/disposal-issue branch May 27, 2022 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants