-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Support non-linear migrations #278
Comments
Back-filling context from a related issue:
|
Same problem. Developer A create migration file on branch issue-a, version is: 20190813143726 Currently, if issue-b release before issue-a, the migration 20190813143726 will be ignored. |
This is not the same problem as this case can be caught and made linear before deploy/shipping. We don't have a fix for this in |
We maintains 2 versions of an application:
v1.0 released with 10_schema.up.sql
v2.0 released with 10_schema.up.sql and 20_schema.up.sql
We found a bug in v1.0 and fixed it by changing database schema, so we released v1.1 with 10_schema.up.sql and 11_schema.up.sql.
But when users trying to upgrade v1.1 to v2.0, we got the "file does not exist" error as there is no 11_schema.up.sql in release v2.0. How can we handle this? Does checking the existence of 11_schema.up.sql make sense?
The text was updated successfully, but these errors were encountered: