Bugfix: Restore original connection after iterating through connections#184
Merged
ka8725 merged 3 commits intowidefix:mainfrom Mar 28, 2026
Merged
Conversation
…rough connections
…gh connection_pool
Member
|
@tony-pizza thanks for your contribution! |
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
2 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.
We use multiple databases. I experienced an error after installing this gem where our application was attempting to fetch data from a table in the incorrect database. I believe it is due to the original connection not getting restored in the
eachmethod in MigrationContext. I've tested this in my application with a monkeypatch.