Allow calling release on connection removed from pool #604
Conversation
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
felixge
added a commit
that referenced
this pull request
Oct 4, 2013
…tion Allow calling release on connection removed from pool
|
@dougwilson 💖 thx! |
|
thanks! |
dveeden
pushed a commit
to dveeden/mysql
that referenced
this pull request
Jan 31, 2023
* add RejectReadOnly * update README.md * close connection explicitly before returning ErrBadConn for 1792 (mysqljs#2) * add test and improve doc * doc/comment changes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This adds a guard on
PoolConnection.prototype.releaseto do nothing when the connection is no longer in the pool. This allows code to unconditionally callreleaseon connections like responsible code even when the connection encountered an error or ended and was thus removed from the pool already.Fixes #589