"General error: 1005 Can't create table" Using Laravel Schema Build and Foreign Keys

Question

Essentially, I am having the same issue as this guy, minus the table prefix. Because I have no table prefix, his fix does not work. http://forums.laravel.com/viewtopic.php?id=972

I am trying to build a table using Laravel's Schema Builder like this:

Schema::create('lessons', function($table)
{
    $table->increments('id');
    $table->string('title')->nullable();
    $table->string('summary')->nullable();
    $table->timestamps();
});

Schema::create('tutorials', function($table)
{
    $table->increments('id');
    $table->integer('author');
    $table->integer('lesson');
    $table->string('title')->nullable();
    $table->string('summary')->nullable();
    $table->string('tagline')->nullable();
    $table->text('content')->nullable();
    $table->text('attachments')->nullable();
    $table->timestamps();
});

Schema::table('tutorials', function($table)
{
    $table->foreign('author')->references('id')->on('users');
    $table->foreign('lesson')->references('id')->on('lessons');
});

The issue is, when I run this code (in a /setup route), I get the following error:

SQLSTATE[HY000]: General error: 1005 Can't create table 'tutorials.#sql-2cff_da' (errno: 150)

SQL: ALTER TABLE `tutorials` ADD CONSTRAINT tutorials_author_foreign FOREIGN KEY (`author`) REFERENCES `users` (`id`)

Bindings: array (
)

Based on posts around the web and the limited documentation available on how to setup Laravel's Eloquent relationships, I'm not sure what I'm doing wrong...

users already exists and it does have an id field that is auto_increment. I am also setting up my models with the proper relationships (belongs_to and has_many), but as far as I can tell this is not the issue-- it's the database setup. The DB is InnoDB.

What exactly am I doing wrong with the foreign key?

Answer 1

I'm not 100% sure if these are the reasons this is failing but a couple of pointers. If you're using an older version of mySQL as the database, the default table implementation is myISAM that does not support foreign key restraints. As your scripts are failing on the foreign key assignment, you are better off explicitly stating that you want INNODB as the engine using this syntax in Schema's create method.

Schema::create('lessons', function($table)
{
    $table->engine = 'InnoDB';

    $table->increments('id');
    $table->string('title')->nullable();
    $table->string('summary')->nullable();
    $table->timestamps();
});

This should hopefully alleviate the problems you are having.

Also, whilst you can declare foreign keys as an afterthought, I create the foreign keys within the initial schema as I can do an easy check to make sure I've got the right DB engine set.

Schema::create('tutorials', function($table)
{
    $table->engine = 'InnoDB';

    $table->increments('id');
    $table->integer('author');
    $table->integer('lesson');
    $table->string('title')->nullable();
    $table->string('summary')->nullable();
    $table->string('tagline')->nullable();
    $table->text('content')->nullable();
    $table->text('attachments')->nullable();
    $table->timestamps();

    $table->foreign('author')->references('id')->on('users');
    $table->foreign('lesson')->references('id')->on('lessons');
});

Hope this helps / solves your problem.

Answer 2

I've been having the same problem. I just noticed the following note at the very bottom of the Laravel Schema docs:

Note: The field referenced in the foreign key is very likely an auto increment and therefore automatically an unsigned integer. Please make sure to create the foreign key field with unsigned() as both fields have to be the exact same type, the engine on both tables has to be set to InnoDB, and the referenced table must be created before the table with the foreign key.

For me, as soon as I set my foreign key fields as such:

$table->integer('author')->unsigned();

I had no problem.

EDIT: Also, make sure that the fields in the foreign table are already created, otherwise this may fail with the same error.

Answer 3

A Summary of the answers already listed, plus mine:

1. Foreign Keys generally require InnoDb, so set your default engine, or explicitly specify

   $table->engine = 'InnoDB';
   

2. Foreign keys require the referenced table to exist. Make sure the referenced table is created in an earlier migration, prior to creating the key. Consider creating the keys in a separate migration to be sure.

3. Foreign Keys require the data type to be congruent. Check whether the referenced field is the same type, whether its signed or unsigned, whether it's length is the same (or less).

4. If you are switching between hand-coding migrations, and using generators, make sure you check the id type you are using. Artisan uses increments() by default but Jeffrey Way appears to prefer integer('id', true).

Answer 4

I ran into this issue too.

The solution I found is that the tables that contain the id that is being used a foreign id needs to be created before another table can reference it. Basically, you are creating a table and telling MySQL to reference another table's primary key but that table doesn't exist yet.

In your example, the author and lesson tables need to be created first.

The order in which the tables are created is dependent on artisan and the order you created your migration files.

My opinion would be to empty out your database of all the tables and change the timestamps in the migration file names (or delete them and recreate them in the correct order) so that your author and lesson tables are created before your tutorials table.

Answer 5

I received the same error because I forgot to set the table type to InnoDB on the referenced table:

$table->engine = 'InnoDB';

Answer 6

Laravel5, MySQL55, CentOS65

in my case the errors were same as this.

Error: [Illuminate\Database\QueryException]
SQLSTATE[HY000]: General error: 1005 Can't create table 'nabsh.#sql-5b0_e' (errno: 121) (SQL: alter table usermeta add constraint usermeta_uid_foreign foreign key (uid) ref erences users (id) on delete cascade).

I found a good tip in this problem's approved answer: ERROR: Error 1005: Can't create table (errno: 121)

Tip: You will get this message if you're trying to add a constraint with a name that's already used somewhere else.

in my case this error means the constraint which has been tried to add is already exists somewhere (but i couldn't see them anywhere).

I copied the output error query and execute it within sequel pro, then hopefully I saw the same error again. as the tip says I changed the constraint name to something else then it affected with no error so there's a problem with constraint name builder in laravel5 + MySQL55 + CentOS65.

Solution: try to rename constraints by sending the second parameter at foreign method in table schema.

Schema::table('tutorials', function($table)
{
    $table->foreign('author')->references('id')->on('users');
    $table->foreign('lesson')->references('id')->on('lessons');
});

to ->

Schema::table('tutorials', function($table)
{
    $table->foreign('author', 'fk_tutorials_author')->references('id')->on('users');
    $table->foreign('lesson', 'fk_tutorials_lesson')->references('id')->on('lessons');
});

i hope it helps. it works in my case

Answer 7

Easiest way is to disable foreign key checks:

DB::statement('set foreign_key_checks=0');

Schema::table( ... );

DB::statement('set foreign_key_checks=1');

Answer 8

This happened to me in Yii Framework 1.x migrations too. Turned out that similarily to the Laravel solutions above it may be caused by a

• wrong spelled (or not yet existing) table name
• wrong spelled (or not yet existing) column name
• duplicate foreign key name in the same database being used in different tables

Answer 9

when using foreign key-s make sure that your foreign key is unsigned. this worked for me

Answer 10

Here's what I do in Laravel 5:

// CREATING TABLE
Schema::create('your_table_name', function (Blueprint $table) {
    $table->engine = 'InnoDB';
    $table->increments('id'); // index field example sample
    $table->string('field2'); // some varchar/string field sample
    $table->integer('field3'); // some integer field sample
    $table->integer('field_some_table_id')->unsigned; //for field that contains foreign key constraint
});

// FOREIGN KEY CONSTRAINT
Schema::table('stock', function ($table) {
    $table->foreign('field_some_table_id')->references('id')->on('some_table')->onDelete('cascade')->onUpdate('cascade');
});

That's all for the conclusion, and it works for me.

Answer 11

You have to give the integer an unsigned flag in Laravel 5.4, like this:

public function up()
{
    Schema::create('posts', function (Blueprint $table) {
        $table->increments('post_id');
        $table->text('title');
        $table->text('text');
        $table->integer('employee_post_id_number')->unsigned();
        $table->foreign('employee_post_id_number')->references 
        ('employee_id_number')->on('employees');
        $table->timestamps();
    });
}

Answer 12

Basically, you get this error because the migration command creates tables in an order which does not match the FK reference you are providing for tables.

Like if you want to create an FK which should refer to the id in users table then users table must exist.

In your example, the author and lesson tables need to be created first.

So, I solved this by creating the tables (one by one) in such order, where I can successfully refer the FK to an existing table. So that Php Artisan Migration cannot decide the order.

Another solution is, you can simply rename the tables or the timestamps provided by migration command .

Answer 13

By using:

 $table->unsignedInteger('author');

instead of:

 $table->integer('author');

the problem will be solved.

The problem is that integer generates an int(11) variable while you need an int(10) variable. unsignedInteger will make it for you.

Answer 14

One of the reasons for this error can be the time and date creation of the migration files. For example , if we have tasks which belongs to some tasks groups, and there is references like: "create_tasks_table

$table->id();
        $table->string('task_name');
        $table->integer('task_group')->unsigned();
        $table->foreign('task_group')
            ->references('id')->on('tasks_groups')->onDelete('cascade');
        $table->longText('task_desc');...."

it is important to create migration file for tasks_groups first (in the name of file we can see the time and date of creation) and than we should create tasks which belongs to some tasks_groups

also it is better to form the migration files with relations like this:

enter codeOne of the reasons for this error can be the time and date creation of the migration files. For example , if we have tasks which belongs to some tasks groups, and there is references like:

"create_tasks_table

        $table->id();
        $table->string('task_name');
        $table->integer('task_group')->unsigned();
        $table->foreign('task_group')
            ->references('id')->on('tasks_groups')->onDelete('cascade');
        $table->longText('task_desc');...."

it is important to create migration file for tasks_groups first (in the name of file we can see the time and date of creation) and than we should create tasks which belongs to some tasks_groups

also

migration table should look like this

`use Illuminate\Database\Migrations\Migration; use Illuminate\Database\Schema\Blueprint; use Illuminate\Support\Facades\Schema;

class CreateTasksTable extends Migration { /** * Run the migrations. * * @return void */ public function up() { Schema::create('tasks_groups', function (Blueprint $table) { $table->increments('id'); $table->string('group_name'); $table->string('slug'); $table->timestamps(); });

    Schema::create('tasks', function (Blueprint $table) {
        $table->id();
        $table->string('task_name');
        $table->integer('task_group')->unsigned();
        $table->foreign('task_group')
            ->references('id')->on('tasks_groups')->onDelete('cascade');
        $table->longText('task_desc');
        $table->string('izvrsioc');
        $table->string('ulogovani_rukovodioc');
        $table->date('time_finishingtask');
        $table->string('prioritet_izrade')->default('');
        $table->string('file_1')->nullable();
        $table->string('file_path1')->nullable();
        $table->string('file_2')->nullable();
        $table->string('file_path2')->nullable();
        $table->string('file_3')->nullable();
        $table->string('file_path3')->nullable();
        $table->longText('dodatni_komentar');
        $table->boolean('zavrsen_task')->default(false);
        $table->boolean('otkazan_task')->default(false);
        $table->timestamps();
    });
}

/**
 * Reverse the migrations.
 *
 * @return void
 */
public function down()
{
    Schema::dropIfExists('tasks');
    Schema::dropIfExists('tasks_groups');
}

}`

it is better if there is relation