This repository was archived by the owner on Jun 28, 2018. It is now read-only.
add option to choose a timestamp format for migration files in CLI #329
Conversation
This file contains hidden or 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
alex-bogomolov
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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 the Unix timestamp is the only option while generating migration files. This PR adds an option to choose a datetime format for the migration timestamp.
I have added the
-timestampoption forcreateaction:For example, for Jan 18th 2018, 18:19:03 the datetime migration timestamp will be
180117181903, while the standard Unix timestamp will be1516205943.In some cases, datetime timestamps are more convenient to work with. If
-timestampflag is not supplied, the default Unix timestamp will be used.