Migrate --pretend can actually create schema unless protected $connection is included in the migration #9059
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 Issue 36596 it was reported that the
php artisan migrate --pretend
command will create schema elements on non-default database connections if the migration doesn't contain aprotected $connection
declaration.This PR seeks to improve the Laravel 10.x documentation to address this apparent bug with
php artisan migrate --pretend
discussed in that thread.@taylorotwell actually said, in part,
This PR seeks to make good on that promise, and prevent others (like me) from missing this information for any project with multiple databases.