Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update CreateMigration time to UTC #38

Closed
wants to merge 1 commit into from
Closed

Update CreateMigration time to UTC #38

wants to merge 1 commit into from

Conversation

duffn
Copy link
Contributor

@duffn duffn commented May 5, 2017

The timestamp used on files when using create should be in UTC.
Developers may be distributed across timezones and so the time
should be standardized and not rely on local time.

The timestamp used on files when using `create` should be in UTC.
Developers may be distributed across timezones and so the time
should be standardized and not rely on local time.
Copy link
Collaborator

@VojtechVitek VojtechVitek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, we might drop the timestamps in favor of incrementing the version numbers. See #27

@duffn
Copy link
Contributor Author

duffn commented May 6, 2017

After reading #25, it looks like the proposed sequential creation of migration files is optional only, correct?

@VojtechVitek
Copy link
Collaborator

@duffn yea, I think so. It's just what filename would "create" command choose by default.

The comparison logic would stay the same.

@duffn
Copy link
Contributor Author

duffn commented May 6, 2017

Cool. Then I think this PR is still valid then.

@VojtechVitek
Copy link
Collaborator

Superseded by #50. Thanks for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants