Add flag to increment by arbitrary integer #957
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.
Summary
Allow users to increment sequential migrations by an arbitrary integer, with 1 as the default.
This leaves rooms for users to use serial migrations, but if they need to insert one betwixt to existing migrations, they do not have to renumber all of the proceeding migrations. A common pattern when making network rules is to increment by 100 for this very reason.
By default, the current behavior will continue.
Example
Why?
When starting a new project and creating many migrations, I often find myself forgetting to make a migration/table that is required to satisfy a foreign key constraint on one of my tables.