Hi all,
I've read all the issues here, and I understand that the artisan module:migrate command respects the priority set in the module.json files in each module, but when I run the
artisan migrate:fresh
command it also execute the migration from the modules, but then it doesn't respect the priorities and perform them in alphabetical order.
I can't find a configuration to ignore modules migrations when running the global artisan migrate:fresh command, therefore (since some modules migrations have foreign keys to another module table) it fails as it tries to migrate the modules in the "wrong" order.
Is there a way to let the migrate:fresh honor the priorities set in each model or to ignore the models migration at all? (I would then run the module:migrate artisan comand to finish it up)
Hi all, I've read all the issues here, and I understand that the artisan module:migrate command respects the priority set in the module.json files in each module, but when I run the
command it also execute the migration from the modules, but then it doesn't respect the priorities and perform them in alphabetical order.
I can't find a configuration to ignore modules migrations when running the global artisan migrate:fresh command, therefore (since some modules migrations have foreign keys to another module table) it fails as it tries to migrate the modules in the "wrong" order.
Is there a way to let the migrate:fresh honor the priorities set in each model or to ignore the models migration at all? (I would then run the module:migrate artisan comand to finish it up)
Thanks!