Summary of some common errors in laravel migrate

The following tutorial column of Laravel will introduce you to some common mistakes and solutions for beginners of laravel migrate. I hope it will be helpful to everyone!

Preface

I have recently started to learn laravel intermittently. I want to create a simple address book system and set up two tables, one for branches and one for contacts. When creating the migration file, I didn't think carefully and first created the contacts table. The contacts table has a foreign key connected to the branches' IDs. As a result, when executing the migrate command, the following error occurred:

[Illuminate\Database\QueryException] 
 
SQLSTATE[HY000]: General error: 1215 Cannot add foreign key constraint (SQL: alter table `contacts` add constraint `contac 
 
ts_branch_id_foreign` foreign key (`branch_id`) references `branches` (`id`) on delete cascade) 
 
[PDOException] 
 
SQLSTATE[HY000]: General error: 1215 Cannot add foreign key constraint

Initial suspicion It was caused by irregular table creation. Therefore, I manually modified the date on the migration file name of branches, and then executed

php artisan migrate:reset

and the following error occurred:

[ErrorException] 
 
include(/Users/Ade/www/laravel_phonebook5.2): failed to open stream: Operation now in progress

failed to open Stream error resolution

It’s not very understandable just by looking at the error message. Let’s check laravel’s log file

more storage/logs/laravel.log

to find the paragraph where ERROR appears:

[2016-09-29 18:05:35] local.ERROR: exception 'ErrorException' with message 'include(/Users/Ade/www/laravel_phonebook5.2): failed to open stream: Operation now in progress' in /Users/Ade/www/laravel_phonebook5.2/vendor/composer/ClassLoader.php:412 
Stack trace: 
#0 /Users/Ade/www/laravel_phonebook5.2/vendor/composer/ClassLoader.php(412): Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(2, 'include(/Users/...', '/Users/Ade/www/...', 412, Array) 
#1 /Users/Ade/www/laravel_phonebook5.2/vendor/composer/ClassLoader.php(412): Composer\Autoload\includeFile() 
#2 /Users/Ade/www/laravel_phonebook5.2/vendor/composer/ClassLoader.php(301): Composer\Autoload\includeFile('/Users/Ade/www/...') 
#3 [internal function]: Composer\Autoload\ClassLoader->loadClass('CreateBranchesT...') 
#4 /Users/Ade/www/laravel_phonebook5.2/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(335): spl_autoload_call('CreateBranchesT...') 
#5 /Users/Ade/www/laravel_phonebook5.2/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(227): Illuminate\Database\Migrations\Migrator->resolve('2016_09_12_1728...') 
#6 /Users/Ade/www/laravel_phonebook5.2/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(206): Illuminate\Database\Migrations\Migrator->runDown(Object(stdClass), false)

The error appeared in line 412 of the ClassLoader.php file

Looking at the changed code, it was found to be a statement calling a file:

This file has been pointed out in the log file, namely resolve('2016_09_12_1728...') . The name prompted by the log is the name of the migration file of the branch I modified.

Let’s search where normal migration files appear:

mdfind 2014_10_12_000000_create_users_table.php|grep phonebook

It can be seen that there are 3 places where normal migration files appear. Modify Only appeared in 1 place.

Edit these two files that do not appear

Adjust the autoload_static.php file

I found that in the vendor/composer/autoload_static.php file, the statements related to branches are as follows:

'CreateBranchesTable' => __DIR__ .,

I think it was when I changed the name, PHP Storm automatically helped me delete all the branches file paths in this file. Lost. Just add it back.
Refer to the configuration of the normal migration file name, add the following

'CreateBranchesTable' => __DIR__ . '/../..' . '/database/migrations/2016_09_12_172822_create_branches_table.php',

Adjust the autoload_classmap.php file

We found In the autoload_classmap.php file, the path name of branches is still the path before modification:

'CreateBranchesTable' => $baseDir . '/database/migrations/2016_09_29_172822_create_branches_table.php',

Modify it to

'CreateBranchesTable' => $baseDir . '/database/migrations/2016_09_12_172822_create_branches_table.php',

and then execute the migrate command

php artisan migrate:reset

OK, the error just now is gone, but we found that the contacts table was not rolled back,

Analysis of failed rollback of contacts

Connect to the database through sequel pro to view

It is found that the contacts table does exist, but there is no content in the migration table. I must execute the previous migrate again An error occurred during the command, and the execution records of contacts were not written to the migrations table. We can re-execute the migrate command and give it a try. First manually delete these two tables, that is, clear the database, and then execute:

php artisan migrate

Let’s ignore the error in creating the contacts table, refresh sequel pro and check:

Sure enough, there is no creation record of contacts in the migration table, which is why there is no rollback operation of contacts when executing reset.

contacts Unable to create branch_id foreign key solution

Now that we have executed the migrate command, let’s start again Take a look at this earliest error:

[Illuminate\Database\QueryException] 
 
SQLSTATE[HY000]: General error: 1215 Cannot add foreign key constraint (SQL: alter table `contacts` add constraint `contacts_branch_id_foreign` foreign key (`branch_id`) references `br 
 
anches` (`id`) on update cascade) 
 
[PDOException] 
 
SQLSTATE[HY000]: General error: 1215 Cannot add foreign key constraint

Calm down and analyze it. Since the prompt is a SQL error, we might as well execute this SQL statement manually in sequel pro.

Sure enough, the execution returned an error.

Check the statement carefully and there is no error. At first thought, it should be caused by the inconsistency between the branch_id type declaration and the ID type in the branches table. Check the structure of contacts and find that Unsigned is not checked. After checking it, execute the SQL statement to add the foreign key and it succeeds.

找到问题原因后，我们就清空数据库，修改 contacts 的 migration 文件，调整 branch_id 为：

$table->integer('branch_id')->unsigned()->comment('机构ID');

再重新执行 migrate 命令，成功!

相关推荐：最新的五个Laravel视频教程

The above is the detailed content of Summary of some common errors in laravel migrate. For more information, please follow other related articles on the PHP Chinese website!