Support multiple databases #52
Merged
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
gaelrenoux
changed the title
|
This is a really nice feature, we needed to do something hacky to work with multiple DB's. I have just one questions for this: |
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 mechanism to support multiple databases in an application (ticket #51).
It does so by providing a
DatabaseT[M]class, whereMis a marker type that can be different for all databases (T is for "Typed"). Not sure if that's the best solution, I welcome remarks on this. I also don't like the nameDatabaseT. I consideredDatabaseCustombut didn't like it either.See the
LayeredAppMultipleDatabasesexample for a demonstration of how to use it.Needs documentation before merging (especially in the README).