Скачать или смотреть How to Remove Pending Migrations in Laravel When Using Multiple Applications

A guide on how to remove pending migrations in Laravel when using two applications with a shared database. Learn how to manually mark migrations as executed to avoid conflicts.
---
This video is based on the question https://stackoverflow.com/q/62564542/ asked by the user 'Belisario Peró' ( https://stackoverflow.com/u/5609097/ ) and on the answer https://stackoverflow.com/a/62564571/ provided by the user 'Kirmin' ( https://stackoverflow.com/u/9252027/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Laravel remove pending migration execution

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Remove Pending Migrations in Laravel When Using Multiple Applications

When working with multiple Laravel applications that utilize the same database, you may encounter some challenges, particularly when it comes to database migrations. If you've migrated migration files from one Laravel app to another, you might find yourself facing a situation where some migrations show up as "pending." This can create confusion and potentially lead to errors when you try to run your database updates.

So, how can you resolve this issue? In this guide, we'll discuss a simple yet effective solution: manually marking those migrations as executed in the database.

Understanding Pending Migrations

What are Migrations?

Migrations in Laravel are like version control for your database. They allow you to define and modify the structure of your database in a fluent, expressive manner. Migrations are usually stored in the migrations table of the database and help keep the database schema in sync across different environments.

Why are Migrations Pending?

When you run php artisan migrate, Laravel checks the migrations table to see which migrations have been applied to the database. If you've moved migration files from one application to another, but the corresponding migrations aren’t marked as executed in the database, they will appear as pending.

Solution: Marking Migrations as Executed

To resolve the issue of pending migrations, you can manually mark the migrations as executed. Here’s how to do it step by step:

Step 1: Access Your Database

You will need to access the database that both Laravel applications are using. You can do this using a database management tool like phpMyAdmin, MySQL Workbench, or through the command line.

Step 2: Locate the Migrations Table

In your database, find the migrations table. This table tracks all the migrations that have been run in your Laravel applications.

Step 3: Identify the Pending Migrations

Identify the pending migrations that you want to mark as executed. Generally, pending migrations will be the ones that you have moved from app 1 to app 2.

Step 4: Manually Insert Migration Records

You need to create new records in the migrations table for each of the migration files you moved. You can do this by running an INSERT statement using SQL. Make sure to insert the migration names and timestamps correctly. Your SQL command might look something like this:

[[See Video to Reveal this Text or Code Snippet]]

Replace 'create_users_table' and 'create_posts_table' with the actual names of your migration files.

The batch number usually represents the execution order; if you're unsure, set it as 1.

Step 5: Run Your Migrations

Once you have marked the migrations, you can now run the php artisan migrate command in Laravel. Since the migrations are marked as executed, Laravel will not attempt to run them again, and you should be free from any pending migration issues.

Conclusion

Managing multiple Laravel applications that utilize the same database can be tricky, especially when it comes to handling migrations. By manually marking the appropriate migrations as executed, you can keep everything in sync and avoid the hassle of pending migrations. Remember to always maintain backups of your data and carefully manage your migrations to ensure your applications run smoothly.

Now that you’re equipped with the knowledge to handle pending migrations, you’ll find it easier to work with multiple Laravel applications and shared databases. Happy coding!