Laravel 5.6.5迁移报错：SQLSTATE[HY000]: General error: 1215 无法添加外键约束

Hey there! Let's work through that foreign key constraint error you're hitting in Laravel migrations—this is one of the most common snags folks run into, and it almost always boils down to a small mismatch or easy-to-fix oversight. Here are the key things to check step by step:

• Mismatched column types
  The foreign key column in your table must exactly match the type of the primary (or unique) key it's referencing in the parent table. For example:

  • If your parent table uses $table->id(); (Laravel's alias for unsignedBigInteger), your foreign key column needs to be $table->unsignedBigInteger('parent_id');—not just bigInteger or integer.
  • Double-check that both columns have the same length, unsigned status, and data type (e.g., char(36) for UUIDs must match on both sides).

• Incorrect migration execution order
  Laravel runs migrations in the order of their file timestamps. If you're trying to create a foreign key to a table that hasn't been created yet (like adding a user_id foreign key to posts before the users table exists), the database can't find the parent table to link to.

  • Fix this by either renaming your migration files to adjust the timestamp order, or manually running the parent table migration first with php artisan migrate --path=/database/migrations/2024_01_01_000000_create_users_table.php.

• Unsupported storage engine
  MySQL's MyISAM engine doesn't support foreign key constraints—you need to use InnoDB (Laravel's default, but it's worth verifying).

  • Check if any of your migration files explicitly set the engine to MyISAM: $table->engine = 'MyISAM';—if so, change it to 'InnoDB'.
  • You can also confirm your database's default engine is InnoDB via your MySQL config or phpMyAdmin.

• Referencing a non-unique column
  Foreign keys can only link to columns that are either a primary key or have a unique index. You can't create a foreign key that references a regular, non-unique column in the parent table.

• Mismatched character sets/collation
  If the parent table and your child table have different character sets or collation rules (e.g., utf8mb4_unicode_ci vs utf8_general_ci), this can break foreign key creation.

  • Ensure both tables use the same character set and collation—you can set this in your migration with $table->charset = 'utf8mb4'; and $table->collation = 'utf8mb4_unicode_ci'; if needed.

• Conflicting onDelete/onUpdate rules (for nullable foreign keys)
  If your foreign key column allows null values, make sure your constraint's onDelete rule aligns with that. For example, if you use ->onDelete('cascade') on a nullable column, you might run into issues—switch to ->onDelete('set null') instead (and ensure the column is set to nullable with ->nullable()).

If you've checked all these and still can't spot the issue, sharing the full code of both the parent table migration and the child table migration would help narrow things down even faster!

内容的提问来源于stack exchange，提问作者radhwan rouihm