Running and rolling back migrations in Ruby on Rails - Step-by-Step Execution

Concept Flow - Running and rolling back migrations

Start: Migration files exist

↓

Run migration command

↓

Rails applies migrations in order

↓

Database schema updated

↓

If rollback needed?

No→End

Yes↓

Run rollback command

↓

Rails reverts last migration

↓

Database schema reverted

↓

End

This flow shows how Rails applies migrations to update the database schema and how it can revert changes by rolling back the last migration.

Execution Sample

Ruby on Rails

rails db:migrate
rails db:rollback

Run migrations to update the database, then rollback the last migration to revert changes.

Execution Table

Step	Command	Action	Migration Status	Database Schema State
1	rails db:migrate	Apply pending migrations	Migration 001 applied	Schema updated with migration 001 changes
2	rails db:migrate	Apply next pending migration	Migration 002 applied	Schema updated with migration 002 changes
3	rails db:rollback	Revert last migration	Migration 002 rolled back	Schema reverted to state after migration 001
4	rails db:rollback	Revert last migration	Migration 001 rolled back	Schema reverted to initial state
5	rails db:rollback	No migrations left to rollback	No change	Schema remains at initial state

💡 No more migrations to rollback, database schema is at initial state

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5
Migration Status	None applied	001 applied	002 applied	001 applied	None applied	None applied
Database Schema State	Initial	Updated with 001	Updated with 002	Updated with 001	Initial	Initial

Key Moments - 2 Insights

Why does rolling back twice revert the schema to the initial state?

Because each rollback reverses the last applied migration step-by-step, so rolling back twice removes both migrations, returning the schema to its original state as shown in execution_table rows 3 and 4.

What happens if you run rollback when no migrations are applied?

No changes occur because there are no migrations to revert, as shown in execution_table row 5 where the schema stays at the initial state.

Visual Quiz - 3 Questions

Look at the execution table, what is the migration status after step 2?

A Migration 001 rolled back

B Migration 002 applied

C No migrations applied

D Migration 002 rolled back

💡 Hint

Check the 'Migration Status' column at step 2 in the execution_table.

At which step does the database schema revert to the initial state?

A Step 3

B Step 2

C Step 4

D Step 1

💡 Hint

Look at the 'Database Schema State' column in execution_table rows for when it shows 'Initial'.

If you run 'rails db:migrate' after step 4, what will happen?

A Migrations 001 and 002 will be applied again

B No migrations will run because all are applied

C Only migration 002 will be applied

D Only migration 001 will be applied

💡 Hint

After step 4, no migrations are applied, so running migrate applies all pending migrations again.

Concept Snapshot

rails db:migrate: Applies all pending migrations in order to update the database schema.
rails db:rollback: Reverts the last applied migration, stepping back the schema.
Multiple rollbacks undo migrations one by one.
If no migrations applied, rollback does nothing.
Use these commands to manage schema changes safely.

Full Transcript

This visual execution shows how Rails runs and rolls back migrations. First, running 'rails db:migrate' applies migrations in order, updating the database schema step-by-step. Each migration changes the schema, tracked in the migration status. If you need to undo changes, 'rails db:rollback' reverts the last migration, restoring the schema to the previous state. Rolling back multiple times removes migrations one by one until the schema returns to its initial state. If no migrations are applied, rollback does nothing. This process helps manage database changes safely and predictably.