Running and rolling back migrations in Laravel - Cheat Sheet & Quick Revision

Recall & Review

beginner

What command do you use to run all pending migrations in Laravel?

Use php artisan migrate to run all migrations that have not been applied yet. This updates your database schema to the latest version.

beginner

How do you rollback the last batch of migrations in Laravel?

Use php artisan migrate:rollback to undo the last batch of migrations that were run. This helps if you want to revert recent database changes.

intermediate

What does the migrate:reset command do?

The php artisan migrate:reset command rolls back all migrations, undoing all database schema changes made by migrations.

intermediate

How can you rollback and then re-run all migrations in one command?

Use php artisan migrate:refresh. It rolls back all migrations and then runs them again, useful for rebuilding the database schema from scratch.

beginner

Why is it important to run migrations carefully in a team environment?

Because migrations change the database structure, running them without coordination can cause conflicts or data loss. Teams should communicate and use version control to keep migrations in sync.

Which command runs all new migrations in Laravel?

A php artisan migrate

B php artisan migrate:rollback

C php artisan migrate:reset

D php artisan migrate:refresh

The php artisan migrate command applies all pending migrations.

What does php artisan migrate:rollback do?

A Resets all migrations

B Runs all migrations

C Rolls back the last batch of migrations

D Refreshes the database

It undoes the last batch of migrations that were applied.

Which command rolls back all migrations at once?

A php artisan migrate:reset

B php artisan migrate:refresh

C php artisan migrate

D php artisan migrate:rollback

migrate:reset rolls back all migrations.

How do you rollback and re-run all migrations in one step?

A php artisan migrate:rollback

B php artisan migrate:reset

C php artisan migrate

D php artisan migrate:refresh

migrate:refresh rolls back all migrations and runs them again.

Why should teams coordinate when running migrations?

A Because migrations are slow

B To avoid database conflicts and data loss

C To speed up migration commands

D Because migrations only run once

Coordination prevents conflicts and data loss when multiple people change the database.

Explain how to run migrations and rollback the last batch in Laravel.

Think about commands to apply and undo changes.

Describe the difference between migrate:reset and migrate:refresh commands.

One just undoes, the other undoes and reapplies.