Why Running and rolling back migrations in Laravel? - Purpose & Use Cases

The Big Idea

What if you could fix database mistakes with a single command instead of hours of manual work?

The Scenario

Imagine you have to create and update your database tables by writing raw SQL commands every time you change your app's data structure.

Then, if something goes wrong, you must manually undo those changes without any easy way to track what was done.

The Problem

Manually running SQL commands is risky and slow.

You can easily forget which changes were applied or make mistakes when trying to undo them.

This leads to inconsistent databases and wasted time fixing errors.

The Solution

Laravel migrations let you write database changes as code that you can run or roll back safely.

This keeps track of every change and lets you move your database forward or backward with simple commands.

Before vs After

✗ Before

CREATE TABLE users (id INT, name VARCHAR(100));
-- To undo: DROP TABLE users;

✓ After

php artisan migrate
php artisan migrate:rollback

What It Enables

You can easily manage database changes across different environments and team members without confusion or errors.

Real Life Example

When adding a new feature that needs a new table, you write a migration and run it on your local machine, then your teammates run the same migration to update their databases automatically.

Key Takeaways

Manual database changes are error-prone and hard to track.

Migrations automate applying and undoing database changes safely.

This keeps your database consistent and your team in sync.

Practice

1. What does the Laravel command php artisan migrate do?

easy

A. It applies all pending migrations to update the database schema.

B. It deletes all tables from the database.

C. It rolls back the last batch of migrations.

D. It creates a new migration file.

Solution

1. Step 1: Understand the purpose of migrations

   Migrations are used to update the database structure safely by applying changes.

2. Step 2: Identify the command effect

   The command php artisan migrate applies all new migrations that have not been run yet.

3. Final Answer:

   It applies all pending migrations to update the database schema. -> Option A

4. Quick Check:

   Running migrations = apply changes [OK]

Hint: Migrate means apply new changes to the database [OK]

Common Mistakes:

• Confusing migrate with rollback
• Thinking migrate deletes tables
• Assuming migrate creates files

2. Which of the following is the correct command to roll back the last batch of migrations in Laravel?

easy

A. php artisan migrate:run

B. php artisan migrate:reset

C. php artisan migrate:refresh

D. php artisan migrate:rollback

Solution

1. Step 1: Identify rollback command

   The command to undo the last batch of migrations is php artisan migrate:rollback.

2. Step 2: Differentiate from other commands

   migrate:reset rolls back all migrations, migrate:refresh rolls back and re-runs all, and migrate:run is invalid.

3. Final Answer:

   php artisan migrate:rollback -> Option D

4. Quick Check:

   Rollback = undo last batch [OK]

Hint: Rollback undoes last batch, reset undoes all [OK]

Common Mistakes:

• Using migrate:reset to rollback last batch
• Confusing migrate:refresh with rollback
• Typing migrate:run which is invalid

3. Given these commands run in order:
php artisan migrate
php artisan migrate:rollback
What is the state of the database migrations after these commands?

medium

A. All migrations are applied.

B. No migrations are applied.

C. Only the last batch of migrations is undone.

D. Migrations are partially applied and partially undone randomly.

Solution

1. Step 1: Apply migrations with migrate

   The first command applies all pending migrations, updating the database.

2. Step 2: Rollback last batch

   The second command undoes only the last batch of migrations applied, not all.

3. Final Answer:

   Only the last batch of migrations is undone. -> Option C

4. Quick Check:

   Rollback undoes last batch only [OK]

Hint: Rollback only undoes last batch, not all [OK]

Common Mistakes:

• Thinking rollback removes all migrations
• Assuming rollback does nothing
• Believing migrations are randomly undone

4. You run php artisan migrate:rollback but get an error saying "No migrations to rollback." What is the most likely cause?

medium

A. There are no migrations applied yet to rollback.

B. The migration files are missing from the migrations folder.

C. You need to run php artisan migrate:reset first.

D. The database connection is not configured.

Solution

1. Step 1: Understand rollback error

   The error means Laravel found no migrations recorded as applied to undo.

2. Step 2: Check migration status

   If no migrations were run before, rollback cannot undo anything, causing this error.

3. Final Answer:

   There are no migrations applied yet to rollback. -> Option A

4. Quick Check:

   No applied migrations = rollback error [OK]

Hint: Rollback needs applied migrations to undo [OK]

Common Mistakes:

• Assuming rollback works without applied migrations
• Thinking reset is needed before rollback
• Ignoring database connection issues

5. You want to undo all migrations and then re-run them fresh. Which command should you use?

hard

A. php artisan migrate:rollback

B. php artisan migrate:refresh

C. php artisan migrate:reset

D. php artisan migrate:fresh

Solution

1. Step 1: Understand the commands

   migrate:rollback undoes last batch, migrate:reset undoes all, migrate:refresh undoes all then re-runs, migrate:fresh drops all tables and migrates.

2. Step 2: Choose command for undo and re-run

   migrate:refresh is the command that rolls back all migrations and then runs them again fresh.

3. Final Answer:

   php artisan migrate:refresh -> Option B

4. Quick Check:

   Refresh = rollback all + migrate again [OK]

Hint: Refresh rolls back all then migrates again [OK]

Common Mistakes:

• Using rollback to undo all migrations
• Confusing reset with refresh
• Using fresh which drops tables instead of rollback