Laravel5.1请求未知数据库类型枚举-Laravel5.1Unknowndatabasetypeenumrequested

28  

The official Laravel 5.1 documentation states:

Laravel 5.1官方文档指出：

Note: Renaming columns in a table with a enum column is not currently supported.

注意：目前不支持使用枚举列重命名表中的列。

It doesn't matter if you're trying to change another column, if the table contains a enum anywhere it won't work. It's a Doctrine DBAL issue.

如果您尝试更改另一列，则无关紧要，如果该表包含枚举，则它将无法正常工作。这是一个Doctrine DBAL问题。

As a workaround you could either drop the column and add a new one (column data will be lost):

作为一种解决方法，您可以删除列并添加一个新列（列数据将丢失）：

public function up()
{
    Schema::table('users', function(Blueprint $table)
    {
        $table->dropColumn('name');
    });

    Schema::table('users', function(Blueprint $table)
    {
        $table->text('username');
    });
}

or use a DB statement:

或使用DB语句：

public function up()
{
    DB::statement('ALTER TABLE projects CHANGE slug url VARCHAR(200)');
}

public function down()
{
    DB::statement('ALTER TABLE projects CHANGE url slug VARCHAR(200)');
}

Source: https://github.com/laravel/framework/issues/1186

资料来源：https：//github.com/laravel/framework/issues/1186

38  

It is a known issue as stated in Laravel 5.1 documentation.

这是Laravel 5.1文档中所述的已知问题。

Note: Renaming columns in a table with a enum column is not currently supported.

注意：目前不支持使用枚举列重命名表中的列。

It happens when you have a enum column in your database table. Whether you are trying to rename another column, or change another column to nullable, this bug will appear. It's an issue with Doctrine\DBAL.

当您在数据库表中有一个枚举列时会发生这种情况。无论您是要重命名另一列，还是将另一列更改为可为空，都会出现此错误。这是Doctrine \ DBAL的一个问题。

An easy fix for this is to just add this constructor method in your database migration file.

一个简单的解决方法是在数据库迁移文件中添加此构造函数方法。

public function __construct()
{
    DB::getDoctrineSchemaManager()->getDatabasePlatform()->registerDoctrineTypeMapping('enum', 'string');
}

This will map all the ENUM columns to VARCHAR(), and the column will accept any string.

这会将所有ENUM列映射到VARCHAR（），该列将接受任何字符串。

This worked for me on Laravel 5.1 and Laravel 5.3. I hope this bug can be fixed soon.

这对Laravel 5.1和Laravel 5.3起了作用。我希望这个bug很快就能解决。

Credit to @Gmatkowski's answer at https://stackoverflow.com/a/32860409/1193201

感谢@ Gmatkowski在https://stackoverflow.com/a/32860409/1193201的回答

2  

A real dirty solution, that gets the job done none the less would be to

一个真正的肮脏的解决方案，无论如何都能完成工作

update Doctrine/DBAL/Schema/MySqlSchemaManager.php 

by ading these lines just above line 113

通过在线113上方的这些线

$this->_platform->registerDoctrineTypeMapping('enum', 'string');
$type = $this->_platform->getDoctrineTypeMapping($dbType);

Beware that updating vendor files directly is not advisable because in the event the vonder chooses to update the plugin, you changes could be overwritten

请注意，不建议直接更新供应商文件，因为如果vonder选择更新插件，您的更改可能会被覆盖