You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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 weregoose create
d.I'm sure I'm missing something here.
Thanks!
The text was updated successfully, but these errors were encountered: