[5.5] Fix order of run migrations #20986
Merged
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.
When you run migration
first
and then you add package to your application that has migration:
and you run this, in database you should have
When you now run
because migrations are ordered by migration descending, the
2016_01_01_000000_create_users_table.php
will be rolled back what could be quite surprising.That's why the sorting order should by first by batch descending and then by migration descending to rollback migrations in the order they were run.