Add --sort (version or applied) to dbmigrator list
#51
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
karenc
force-pushed
the
list-by-applied
branch
from
2d673b1
to
460a5d2
Compare
`dbmigrator list` only shows migrations in the order of migration filenames at the moment. It works well for when users are trying to migrate. When users are trying to rollback however, it is difficult to tell which migration will be rolled back because the applied dates are not in the same order as the migration filenames. This change allows the user to specify the order by doing `--sort=applied`: ``` version | name | is applied | date applied ---------------------------------------------------------------------- 20160228212456 cool_stuff True 2017-10-20 10:27:57.011677-07:00 20160228202637 add_table False ```
karenc
force-pushed
the
list-by-applied
branch
from
460a5d2
to
e736e71
Compare
mmulich
approved these changes
Dec 5, 2017
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.
dbmigrator listonly shows migrations in the order of migrationfilenames at the moment. It works well for when users are trying to
migrate. When users are trying to rollback however, it is difficult to
tell which migration will be rolled back because the applied dates are
not in the same order as the migration filenames.
This change allows the user to specify the order by doing
--sort=applied: