Why is having more than one connection such a pain?

[K2ouMais]

Hello everyone,

I am writing here and hope someone can somehow explain this to me.

I have a lot of migrations and seeds and on every seed I use the DB::connection('con2'), so that the right Table can be seeded.

On the first run with php artisan migrate --seed everything works as expected.

On all runs after that only php artisan migrate:refresh --seed will work.

If I run php artisan migrate:fresh --seed I get presented that the table is already available.

Even if I do a dump with php artisan schema:dump I see that there is only the tables of the first / standard connection.

Maybe I am missing something, but this is really a pain to work with..

config\database.php:

'default' => env('DB_CONNECTION', 'con1'),

'con1' => [
            'driver' => 'mysql',
            'url' => env('DATABASE_URL_KUNDENVERW'),
            'host' => env('DB_HOST_KUNDENVERW', '127.0.0.1'),
            'port' => env('DB_PORT_KUNDENVERW', '3306'),
            'database' => env('DB_DATABASE_KUNDENVERW', 'mydb1'),
            'username' => env('DB_USERNAME_KUNDENVERW', 'forge'),
            'password' => env('DB_PASSWORD_KUNDENVERW', ''),
            'unix_socket' => env('DB_SOCKET', ''),
            'charset' => 'utf8mb4',
            'collation' => 'utf8mb4_unicode_ci',
            'prefix' => '',
            'prefix_indexes' => true,
            'strict' => true,
            'engine' => null,
            'options' => extension_loaded('pdo_mysql') ? array_filter([
                PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'),
            ]) : [],
        ],

        'con2' => [
            'driver' => 'mysql',
            'url' => env('DATABASE_URL_DATA'),
            'host' => env('DB_HOST_DATA', '127.0.0.1'),
            'port' => env('DB_PORT_DATA', '3306'),
            'database' => env('DB_DATABASE_DATA', 'mydb2'),
            'username' => env('DB_USERNAME_DATA', 'forge'),
            'password' => env('DB_PASSWORD_DATA', ''),
            'unix_socket' => env('DB_SOCKET', ''),
            'charset' => 'utf8mb4',
            'collation' => 'utf8mb4_unicode_ci',
            'prefix' => '',
            'prefix_indexes' => true,
            'strict' => true,
            'engine' => null,
            'options' => extension_loaded('pdo_mysql') ? array_filter([
                PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'),
            ]) : [],
        ],

Migration:

<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

class CreateCountriesTable extends Migration
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::connection('con2')->create('countries', function (Blueprint $table) {
            $table->id();
            $table->string('code', 2)->index();
            $table->string('name', 50);
            $table->timestamps();
        });
    }

    /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        Schema::connection('con2')->dropIfExists('countries');
    }
}

Seeder:

<?php

namespace Database\Seeders;

use App\Models\LeiCountry;
use Illuminate\Database\Seeder;
use DB;

class CountrySeeder extends Seeder
{
    /**
     * Run the database seeds.
     *
     * @return void
     */
    public function run()
    {
        DB::connection('con2')->table('countries')->insert([
            ["code" => "AF", "name" => "Afghanistan"],
            ["code" => "AX", "name" => "Åland Islands"],
            ["code" => "AL", "name" => "Albania"],
            ["code" => "DZ", "name" => "Algeria"],
            ["code" => "AS", "name" => "American Samoa"],
            ["code" => "AD", "name" => "Andorra"],
            ["code" => "AO", "name" => "Angola"],
            ["code" => "AI", "name" => "Anguilla"],
            ["code" => "AQ", "name" => "Antarctica"],
        ]);
    }
}

[haivd-ids]

You don't need to do set connection on every migration and seeder like that.
You can specify the connection to run with --database option.