Raise useful exception when db/migrate directory is absent #156
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.
Currently when you run
bin/rails db:migrate
on a fresh rails appcreated with:
rails new appname --skip-active-record
you don't get adb/migrate
directory which results in this exception:With this fix SequelRails will catch this issue before it's too late and
gets to Sequel's migration logic (which assumes db/migrate exists). This
is the error produced now:
After following the instruction from the error
mkdir -p db/migrate
,you'll then get this much friendlier error from Sequel::Migrator itself: