Default connection for migrations

[aagjalpankaj]

Currently Laravel provides two ways to specify database connection for migrations:

1. In the migrate command e.g. php artisan migrate --database=<connection_name>
2. In the migration itself e.g. Schema::connection('connection_name')->

Otherwise it uses the default connection specified in database.php.

Can we allow specifying default connection just for migrations like below in database.php?

'migrations' => [
        'table' => 'migrations',
        'update_date_on_publish' => true,
        'connection' => env('DB_MIGRATION_CONNECTION'),
    ],

---

What prompts us to trigger this requirement?

We create two separate database connections - one for application and another for migration. Only migration user has DDL permissions. We use laravel automations and that does't allow --database option while executing migrations. So we always need to specify connection explicitly in the migration using Schema::connection('connection_name')->.

I understand that this requirement may seem superfluous and not urgent, but good to see what you guys think about it :)

[Sophist-UK]

My suggestion would be for you to sub-class the Illuminate\Database\Migrations\Migration class such that your sub-class always uses the Schema:connection call.

[aagjalpankaj]

Yes, there are workarounds to achieve it. default option in configuration would be nice to have :)

[Sophist-UK]

My suggestion is not a workaround - it is a solution.

This requirement is NOT a common one - and on that basis is extremely unlikely to be adopted in core Laravel, especially when the above solution is a reasonable one and an easy one and one which fits entirely within the concepts of OO.

[shaedrich]

No harm in having options here—go for it, I'd say 👍🏻