-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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
[5.4] Add support for multiple --path to migrate:reset #18540
Conversation
Similar #7884 |
The behavior of migrate:reset was changed since 5.2 (as least for Lumen), I have an application built on Lumen 5.2 and the next code works for 5.2:
The above code successfully runs all migrations from default migrations dir (/database/migrations) and custom dir (/database/migrations/foobarmodule) and then successfully resets ALL migrations back, this is relevant for version 5.2. But some time ago I upgraded Lumen to 5.4 and the above code fails while resetting migrations:
The
The full stacktrace:
|
Fixed situation when `migrate:reset` is run from application: ``` Artisan::call('migrate:reset', [ '--path' => 'database/migrations', ]); ```
It's required for
migrate:reset
if you run migrations from different paths:./artisan migrate:reset
will fail with something like this:At the same time next code will work (with mine changes):