[10.x] Clarifies connection property #8791
Closed
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.
In light of laravel/framework#21009, and now laravel/framework#47082, it appears that utilizing this particular property can result in inconsistencies. As the "migrations" table exists on the main connection, while one or more particular migrations are applied in different connections.
As solution, I propose we only document the
--database
CLI option. This option effectively ensures the consistent state of migrations by applying all migrations on the same connection.