Update db:migrate:up & db:migrate:down to act more like active record one #200
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
PikachuEXE
changed the title
PikachuEXE
force-pushed
the
feature/run-specific-migration-only
branch
from
f4b0193
to
e9e8e77
Compare
|
Updated test cases to check for running migrations that can only be run with updated rake task
|
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.
I read the description on rake tasks and realize that the actual behaviour is more like sequel one
Which is weird since version is required (no less chance for being more like sequel one to be intended)
From
#96 (comment)
I am not sure if this is what you want though let me know
Also no support for
STEPyetAlso only tested for timestamp versions (not integer versions)