This repository has been archived by the owner on Apr 21, 2022. It is now read-only.
Supporting Multiple Databases #6
Open
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hello,
I added a few small changes and some documentation in the README to support multiple databases per environment in sequel-rails. There is a caching mechanism that makes sure you connect to a database when you first request it, and then for subsequent requests it is reused. I worked on this with Jeremy Evans a bit. In the future it would be good to support nesting multiple databases under each environment. For now I just implemented supporting multiple top level databases. Let me know what you think!
Thanks,
Brandon Hauff