allow db: namespace to be reconfigured to something else, eg sequel: #89
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
|
Sorry for not responding sooner, this is nice addition ! Thanks a lot for your help. |
JonathanTron
added a commit
that referenced
this pull request
Jun 9, 2015
allow db: namespace to be reconfigured to something else, eg sequel:
JonathanTron
added a commit
that referenced
this pull request
Jun 9, 2015
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.
Because of rails_admin, I had to pull ActiveRecord into a project that I'd already configured for Sequel with sequel-rails.
rake db:migratewould fail.This pull request allows the
db:rake namespace to be configured using something likeconfig.sequel.load_database_tasks = :sequel, but preserves existing behaviour.Now I (and capistrano, with some work) can say
rake sequel:migrateand things work as expected.