Why Rolling back migrations in Supabase? - Purpose & Use Cases

The Big Idea

What if you could instantly undo a risky database change with one command?

The Scenario

Imagine you just updated your database with new changes, but suddenly your app breaks because of a mistake in the update.

You try to fix it by manually undoing each change in the database, one by one, hoping nothing else breaks.

The Problem

Manually reversing database changes is slow and risky.

You might forget a step or make a typo, causing more errors.

It's like trying to untangle a knot without knowing how it was tied.

The Solution

Rolling back migrations lets you undo database changes safely and quickly.

It tracks each change and can reverse them automatically, so you don't have to guess or do it by hand.

Before vs After

✗ Before

DROP TABLE users;
ALTER TABLE orders DROP COLUMN discount;

✓ After

supabase db rollback --steps 1

What It Enables

You can fix mistakes instantly and keep your database healthy without stress.

Real Life Example

A developer deploys a new feature but finds a bug in the database schema.

Using rollback, they quickly undo the last migration and fix the bug before users notice.

Key Takeaways

Manual undoing of database changes is error-prone and slow.

Rolling back migrations automates safe reversal of changes.

This keeps your app stable and saves time during fixes.

Practice

1. What does the command supabase db rollback do?

easy

A. It creates a new migration file.

B. It undoes the last applied database migration.

C. It applies all pending migrations to the database.

D. It deletes the entire database.

Solution

1. Step 1: Understand the purpose of rollback

   Rollback means undoing changes, so this command reverses migrations already applied.

2. Step 2: Identify the command effect

   supabase db rollback specifically undoes the last migration applied to the database.

3. Final Answer:

   It undoes the last applied database migration. -> Option B

4. Quick Check:

   Rollback = undo last migration [OK]

Hint: Rollback means undo last migration applied [OK]

Common Mistakes:

• Confusing rollback with applying migrations
• Thinking rollback creates new migrations
• Assuming rollback deletes the database

2. Which of the following is the correct syntax to rollback the last 3 migrations using Supabase CLI?

easy

A. supabase db rollback --steps 3

B. supabase db rollback -n 3

C. supabase rollback db 3

D. supabase db undo 3

Solution

1. Step 1: Recall the rollback command syntax

   The Supabase CLI uses --steps to specify how many migrations to rollback.

2. Step 2: Match the correct option

   supabase db rollback --steps 3 uses supabase db rollback --steps 3, which is the correct syntax.

3. Final Answer:

   supabase db rollback --steps 3 -> Option A

4. Quick Check:

   Use --steps to rollback multiple migrations [OK]

Hint: Use --steps to specify rollback count [OK]

Common Mistakes:

• Using incorrect flags like -n instead of --steps
• Wrong command order like 'rollback db'
• Using 'undo' instead of 'rollback'

3. Given the following commands run in order:
supabase db push
supabase db push
supabase db rollback --steps 1
What is the state of migrations after these commands?

medium

A. All migrations are rolled back except the last one.

B. No migrations are applied.

C. Both migrations are still applied.

D. Only the first migration is applied.

Solution

1. Step 1: Apply two migrations

   Running supabase db push twice applies two migrations in order.

2. Step 2: Rollback one migration

   The rollback with --steps 1 undoes the last applied migration, leaving the first migration applied.

3. Final Answer:

   Only the first migration is applied. -> Option D

4. Quick Check:

   Rollback 1 step removes last migration applied [OK]

Hint: Rollback with --steps 1 undoes last migration only [OK]

Common Mistakes:

• Assuming rollback removes all migrations
• Thinking rollback does not affect applied migrations
• Confusing push and rollback order

4. You run supabase db rollback --steps 2 but get an error saying no migrations to rollback. What is the most likely cause?

medium

A. There are fewer than 2 migrations applied to rollback.

B. The migrations folder is missing.

C. The database connection is not configured.

D. Rollback command requires a --force flag.

Solution

1. Step 1: Understand rollback error

   The error indicates no migrations to rollback, meaning none or fewer than requested are applied.

2. Step 2: Identify cause

   If fewer than 2 migrations are applied, trying to rollback 2 steps causes this error.

3. Final Answer:

   There are fewer than 2 migrations applied to rollback. -> Option A

4. Quick Check:

   Rollback steps > applied migrations causes error [OK]

Hint: Check applied migrations count before rollback steps [OK]

Common Mistakes:

• Assuming rollback always works without applied migrations
• Thinking rollback needs --force flag
• Ignoring database connection issues

5. You have applied 5 migrations but want to rollback only the 3rd migration without affecting others. Which approach is best?

hard

A. Delete the 3rd migration file and run supabase db push.

B. Use supabase db rollback --steps 3 to rollback only the 3rd migration.

C. Rollback all migrations from the 3rd onwards, then reapply the ones after it.

D. Directly edit the database to remove changes from the 3rd migration.

Solution

1. Step 1: Understand migration order

   Migrations apply in order; you cannot rollback a middle migration without undoing later ones first.

2. Step 2: Plan rollback and reapply

   Rollback migrations after the 3rd (steps 2), then rollback the 3rd, then reapply the later migrations.

3. Final Answer:

   Rollback all migrations from the 3rd onwards, then reapply the ones after it. -> Option C

4. Quick Check:

   Rollback middle migration requires undoing later ones first [OK]

Hint: Undo later migrations first, then rollback target migration [OK]

Common Mistakes:

• Trying to rollback a single middle migration directly
• Deleting migration files without rollback
• Editing database manually causing inconsistency