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

help me understand hybrid versioning? #134

Closed
eeshugerman opened this issue Dec 10, 2018 · 2 comments
Closed

help me understand hybrid versioning? #134

eeshugerman opened this issue Dec 10, 2018 · 2 comments

Comments

@eeshugerman
Copy link

I don't see how it is any different than plain-ol' timestamp versioning. From what I can tell, goose fix simply sorts migrations by timestamp and generates incremental version numbers accordingly. If this is automated by CI to take place when code is pushed to production, how is this different, effectively, than timestamp versioning? In either case, the migrations will be run in the order they were goose created.

I'm sure I'm missing something here.

Thanks!

@VojtechVitek
Copy link
Collaborator

Please read the versioning problem.

cc @1vn

@eeshugerman
Copy link
Author

I see, thanks. I realize now that I did not fully understand the versioning problem.

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

No branches or pull requests

2 participants