support mariadb database driver

[mrvnklm]

As of Laravel 11 there is a dedicated mariadb database driver. Using --driver=mysql just works fine as it just restores a dump instead of running column specific migrations, so using mariadb as an alias for mysql would just solve the issue.

[mrvnklm]

What do you think? @stefanzweifel

[stefanzweifel]

@mrvnklm I'm not oposed.

I haven't used mariadb and don't know what "column specific migrations" are or what excatly needs to change to support mariadb as db driver?
I also don't know where you put the --driver=mysql option, as backup:restore doesn't provide this option.

Would be awesome if you could provide guidance, as you seem to know more than I do about mariadb.
It's not documented, but you can add custom DB drivers in userland. Here's the relevant code:
https://github.com/stefanzweifel/laravel-backup-restore/blob/main/src/DbImporterFactory.php#L40-L54

Putting the following code in a service provider should work.

DbImporterFactory::extend('mariadb', new MariaDb);

[mrvnklm]

Thank you for your reply.

I actually ment --connection=mysql whereas the connection has the same env variables prefix DB_ and so on, thats why this works.
MariaDB just have some differences like how JSON columns or UUIDs are handled on migration with the corresponding driver.
For dumping or restoring that doesnt matter, as the mysqldump / mysql command is used to dump and restore an sql file. Thats why having the same impementation for both works just fine, just without having to alias the connection details.

I will have a look into your suggestion.

[stefanzweifel]

Ah, I see. Thanks for the insights.

Then it sounds like we could just add mariadb to the match-statement here: https://github.com/stefanzweifel/laravel-backup-restore/blob/main/src/DbImporterFactory.php#L49.

[mrvnklm]

Yup, that would be a viable solution I think.

[mrvnklm]

Should work for most systems, but there might be environments that might only have mariadb binary instead.