dbal: Unknown database type enum, MySQL57Platform may not support it

In case anyone else comes across this and is similarly dismayed by the complexity of the solutions offered: I had a similar situation trying to do a field change in a Laravel migration (on a field that was not an enum, but in a table that had an enum in a different field). I found that adding this line to the top of the migration’s up() method was sufficient to get the migration to run smoothly:

DB::connection()->getDoctrineSchemaManager()->getDatabasePlatform()->registerDoctrineTypeMapping('enum', 'string');

Closing as duplicate. See:

• https://stackoverflow.com/a/9057352/347063
• https://www.doctrine-project.org/projects/doctrine-orm/en/2.6/cookbook/mysql-enums.html

The database platform needs to be configured to detect any custom types, and ENUMs are indeed custom.

I solved it, dropping the enum column, doing the change and adding the enum column again. But i’m not in production environment.

public function up()
        {
        Schema::table('m_table', function (Blueprint $table) {
            $table->dropColumn('type'); // enum column
        });

        Schema::table('m_table', function (Blueprint $table) {
            $table->integer('idstate')->nullable()->unsigned()->change();
            $table->integer('idcity')->nullable()->unsigned()->change();
        });

        Schema::table('m_table', function (Blueprint $table) {
            $table->enum('type', ['national', 'state', 'municipal'])->after('subtitle');
        });


    }

On Laravel this fix the issue:

use Doctrine\DBAL\Types\Types;
use Illuminate\Database\Migrations\Migration;
use Illuminate\Support\Facades\DB;

class YourEditClass extends Migration
{
    public function __construct()
    {
        DB::getDoctrineSchemaManager()->getDatabasePlatform()->registerDoctrineTypeMapping('enum', Types::STRING);
    }
}

I solve my problem by doing this in the constructor of the migration file //This two has to be together to fix the enum issue

DB::getDoctrineSchemaManager()->getDatabasePlatform()->registerDoctrineTypeMapping('enum', 'string');

Type::hasType('enum') ? Type::hasType('enum') : Type::addType('enum', StringType::class);

Do well to import all class types

I faced the same issue after defining custom enum type as described in doctrine 2.x documentation (I implemented the second solution in the documentation) on Symfony 4.4 . After defining the enum type and migration worked ok. However, I faced this error with consecutive migrations. To solve I created an empty migration file:

final class Version20200508000000 extends AbstractMigration
{
    public function __construct(Version $version)
    {
        parent::__construct($version);
        //this lines solves error, solution provided by @sgilberg 
        $this->connection->getSchemaManager()->getDatabasePlatform()->registerDoctrineTypeMapping('enum', 'string');
    }

    public function getDescription() : string
    {
        return '';
    }

    public function up(Schema $schema) : void
    {
        // this up() migration is auto-generated, please modify it to your needs
    }

    public function down(Schema $schema) : void
    {
        // this down() migration is auto-generated, please modify it to your needs
    }
}

You don’t have to add $this->connection->getSchemaManager()->getDatabasePlatform()->registerDoctrineTypeMapping('enum', 'string'); this line to every migration file. Single migration file containing this line is enough.

There should be a better solution for this problem

@HenryRuiz332 @radoos Not sure if anyone is still paying attention to this, but I’ve ran into this in an unrelated scenario:

1. Using doctrine/migrations standalone, no framework
2. Registering the connectio in an cli-config.php file:

use Symfony\Component\Console\Helper\HelperSet;
use Doctrine\DBAL\Tools\Console\Helper\ConnectionHelper;
use Doctrine\ORM\Tools\Console\Helper\EntityManagerHelper;

$entityManager = get_entity_manager(); //my own function, just building an entity manager here
$conn = $entityManager->getConnection();
$platform = $conn->getDatabasePlatform();

$platform->registerDoctrineTypeMapping('enum', 'string');

return new HelperSet([
    'em' => new EntityManagerHelper($entityManager),
    'db' => new ConnectionHelper($conn),
]);

1. If I dump the platform (an Doctrine\DBAL\Platforms\MySQL57Platform instance), it has an ‘enum’ => string(6) “string” entry in the mappings array.

However, I still get the error.

As a side-note, I am not using any enum in my own models, however the DB has been modified by PMA when I dumped the configuration table it needs and it has an enum field somewhere. If I remove those tables, all is ok.

In case anyone else comes across this and is similarly dismayed by the complexity of the solutions offered: I had a similar situation trying to do a field change in a Laravel migration (on a field that was not an enum, but in a table that had an enum in a different field). I found that adding this line to the top of the migration’s up() method was sufficient to get the migration to run smoothly:

DB::connection()->getDoctrineSchemaManager()->getDatabasePlatform()->registerDoctrineTypeMapping('enum', 'string');

thanks, you are my hero

I solved it, dropping the enum column, doing the change and adding the enum column again. But i’m not in production environment.

@jtpdev Terrible idea. You’ll lost the data. Sollution provided by @sgilberg works, however there is slight chance to use wrong class 😃 My PHPStorm has imported Illuminate\Support\Facades\DB by default and that’s wrong.

@4n70w4 try to use following code

$platform = Schema::getConnection()->getDoctrineSchemaManager()->getDatabasePlatform(); $platform->registerDoctrineTypeMapping('enum', 'string');

In case anyone else comes across this and is similarly dismayed by the complexity of the solutions offered: I had a similar situation trying to do a field change in a Laravel migration (on a field that was not an enum, but in a table that had an enum in a different field). I found that adding this line to the top of the migration’s up() method was sufficient to get the migration to run smoothly:

DB::connection()->getDoctrineSchemaManager()->getDatabasePlatform()->registerDoctrineTypeMapping('enum', 'string');

Interesting… wonder if this could be done automatically by the Laravel’s Schema/Connection.