Good Morning,

Pretty sure this update broke the database part for me - was working with 12.26.4 not with 12.27.0, very basic mariadb setup.

Found issue likely related to your update mentioned here, adding enum support.

Only thing not sure of, is what further up calls DatabaseManager->connection if it is supposed to give the default name, or if the default is to pick up via the config via getDefaultConnection.

Line 97 of DatabaseManager.php (in connection function)

$name = enum_value($name) ?? $this->getDefaultConnection()

Returns blank string, and it throws InvalidArgumentException "Database connection [] not configured", as the name is blank.

Change ?? to ?: though:

$name = enum_value($name) ?: $this->getDefaultConnection()

It returns the config default and works.

Guessing the enum_value is returning string, not null so null coalescing wont work here.

I also found leaving DatabaseManager as deployed you can fix the function enum_value

default match should be:

default => $value ?: value($default)

Rather than

default => $value ?? value($default)

Change ?? to ?: though:

$name = enum_value($name) ?: $this->getDefaultConnection()

It returns the config default and works.

Yeah I figure this 'fixes' the issue; suggested this at #56888 (comment). I still don't know why this is needed though.

Guessing the enum_value is returning string, not null so null coalescing wont work here.

It should not; enum_value should leave null untouched; everything basically should. My assumption is that $name is somehow already an empty string (passed as argument) in the call to connection and was previously converted just like null was.

Can you somehow check if indeed $name is indeed already '' before any logic happens within connection, and if so trace back where this value originates from? Maybe some config default? Or an empty value in .env?

@jnoordsij https://github.com/Flynsarmy/laravel-csv-seeder/blob/master/src/CsvSeeder.php#L37