InvalidArgumentException in database seeders only in ^12.27

[gabrielrbarbosa]

Laravel Version

12.27.0

PHP Version

8.5.0

Database Driver & Version

MariaDB 11.4.8

Description

Database\Seeders\BandeiraCartaoTableSeeder ............................................................................................... RUNNING

InvalidArgumentException

Database connection [] not configured.

at vendor/laravel/framework/src/Illuminate/Database/DatabaseManager.php:221
217▕
218▕ $config = $this->dynamicConnectionConfigurations[$name] ?? Arr::get($connections, $name);
219▕
220▕ if (is_null($config)) {
➜ 221▕ throw new InvalidArgumentException("Database connection [{$name}] not configured.");
222▕ }

Related 1a3c942

Steps To Reproduce

php artisan migrate:fresh --seed
It happens here on a seeder that extends CsvSeeder

[crynobone]

Hey there, thanks for reporting this issue.

We'll need more info and/or code to debug this further. Can you please create a repository with the command below, commit the code that reproduces the issue as one separate commit on the main/master branch and share the repository here?

Please make sure that you have the latest version of the Laravel installer in order to run this command. Please also make sure you have both Git & the GitHub CLI tool properly set up.

laravel new bug-report --github="--public"

Do not amend and create a separate commit with your custom changes. After you've posted the repository, we'll try to reproduce the issue.

Thanks!

[jnoordsij]

A quick glance over this (and #56892) makes it look like changing from ternary to null-coaleascing in 1a3c942 might have broken some configurations, which due to yet unknown pass empty string (instead of null) as connection name.

Changing back all occurences of ?? $this->getDefaultConnection() to ?: $this->getDefaultConnection() should likely resolve this, however the question then remains if empty string should be supported as argument and where it actually originates from. Maybe some empty values in a .env file?

[gabrielrbarbosa]

Here: public string $connection = '';
https://github.com/Flynsarmy/laravel-csv-seeder/blob/master/src/CsvSeeder.php#L37

[tallenglish]

@jnoordsij Just to throw a spanner in to make it even weirder. I am currently using stock 12.27.1 with only one exception to change the function enum_value (src/Illuminate/Collections/functions.php) default match to use ?: not ??

The default value is always null in my case, but the value is usually empty string, and twice null

So the enum_value seeing blank string overrides the null coalesce later in DatabaseManager, so it never tries to get the default from config.

default => $value ?? value($default) <- broken because $value can be empty string

default => $value ?: value($default) <- works and returns null because $default is always null in my case, so allows null coalesce in DatabaseManager to work correctly and pass to looking in config for name.

[03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL <- string breaks this
[03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL
[03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL
[03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL
[03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL
[03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL
[03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL
[03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL
[03-Sep-2025 14:51:38 UTC] enum_value => value: NULL, default: NULL <- these would work
[03-Sep-2025 14:51:38 UTC] enum_value => value: NULL, default: NULL
[03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL

[jnoordsij]

Here: public string $connection = ''; https://github.com/Flynsarmy/laravel-csv-seeder/blob/master/src/CsvSeeder.php#L37

I've created #56906 which should probably resolve this. I think however that probably this source should be changed to

public ?string $connection = null;

to be more accurate.

[jnoordsij]

@jnoordsij Just to throw a spanner in to make it even weirder. I am currently using stock 12.27.1 with only one exception to change the function enum_value (src/Illuminate/Collections/functions.php) default match to use ?: not ??

The default value is always null in my case, but the value is usually empty string, and twice null

So the enum_value seeing blank string overrides the null coalesce later in DatabaseManager, so it never tries to get the default from config.

default => $value ?? value($default) <- broken because $value can be empty string

default => $value ?: value($default) <- works and returns null because $default is always null in my case, so allows null coalesce in DatabaseManager to work correctly and pass to looking in config for name.

[03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL <- string breaks this [03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL [03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL [03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL [03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL [03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL [03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL [03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL [03-Sep-2025 14:51:38 UTC] enum_value => value: NULL, default: NULL <- these would work [03-Sep-2025 14:51:38 UTC] enum_value => value: NULL, default: NULL [03-Sep-2025 14:51:38 UTC] enum_value => value: string, default: NULL

I think enum_value is doing exactly what it should do: if $value === '' then it returns '' and if $value === null then it returns null. The effective change from #56878 however, is in changing from ?: $this->getDefaultConnection() to ?? $this->getDefaultConnection(): previously this would use the default connection if $name was either '' or null, but now only when it is precisely null.