$table->uuid() creates UNKNOWN column type in Laravel 12 migrations with MariaDB, but works as CHAR(36) in MySQL

[filipegomes-acin]

Laravel Version

12.2.0

PHP Version

8.4.2

Database Driver & Version

11.4.4-MariaDB-ubu2404

Description

In Laravel 12, using $table->uuid() in a migration correctly creates a CHAR(36) column in MySQL, but in MariaDB, it results in an UNKNOWN column type.

Steps To Reproduce

On .env

DB_CONNECTION=mariadb

Create a migration:

Schema::create('table_name', function (Blueprint $table) {
     ...
    $table->uuid();
    ...
});

Run migration:

php artisan migrate

Results:

• ✅ MySQL 8+ → Creates CHAR(36) (Works as expected)
• ❌ MariaDB 10.6+ → Creates UNKNOWN column type

[crynobone]

https://laravel.com/docs/11.x/upgrade#dedicated-mariadb-driver

[filipegomes-acin]

Thank you for the information and your work. But I suggested that it be specified in the documentation in the migrations section for uuid while there is no more convenient solution, such as using CHAR(36) when calling $table->uuid() when the selected diver is mariadb.

[filipegomes-acin]

For example, my temporary solution is to make a macro for Blueprint in order to override the uuid method when the connection is MariaDB, but it doesn't work, so for now I will make a "Custom Uuid".

[inmanturbo]

Yeah you cannot override existing methods with macros, only add new ones.