After a connection error, selected db, if it was set, is not restored#142
Merged
Conversation
…store selected db on connect
|
+1 |
|
Solves issue #86 |
mranney
added a commit
that referenced
this pull request
Nov 14, 2011
After a connection error, selected db, if it was set, is not restored
Contributor
|
Thanks. |
Contributor
|
I just published v0.7.0 to npm which includes this fix. |
Author
|
Thanks. |
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
4 participants
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.
override select method to store selected db in client instance and restore selected db on connect when an error happened