Why migrations version your database schema in Supabase - The Real Reasons

The Big Idea

What if every database change could be tracked like saving versions of a document, so nothing ever gets lost or broken?

The Scenario

Imagine you have a team working on a database for a web app. Everyone tries to change the database structure by hand, saving files locally or emailing scripts. It quickly becomes confusing who changed what and when.

The Problem

Manually updating the database schema is slow and risky. Changes can overwrite each other, cause errors, or get lost. It's hard to track history or fix mistakes without a clear record.

The Solution

Migrations with versioning keep a clear, ordered history of every change to the database schema. Each change is saved as a versioned step, so you can apply, review, or roll back updates safely and easily.

Before vs After

✗ Before

ALTER TABLE users ADD COLUMN age INT;
-- Run manually on each environment

✓ After

-- Migration file v002_add_age_column.sql
CREATE TABLE IF NOT EXISTS migrations (id SERIAL PRIMARY KEY, name TEXT, applied_at TIMESTAMP);
ALTER TABLE users ADD COLUMN age INT;
INSERT INTO migrations (name, applied_at) VALUES ('v002_add_age_column', NOW());

What It Enables

It enables teams to collaborate smoothly, track every database change, and keep all environments in sync without confusion or errors.

Real Life Example

A startup growing fast needs to update its database often. Using versioned migrations, developers add new features without breaking the app or losing data, even when working from different locations.

Key Takeaways

Manual database changes cause confusion and errors.

Versioned migrations track every schema change clearly.

This keeps all environments consistent and safe.

Practice

1. Why do migrations use version numbers or timestamps to track database schema changes?

easy

A. To keep changes in the correct order and avoid conflicts

B. To make the database run faster

C. To reduce the size of the database

D. To hide the changes from users

Solution

1. Step 1: Understand the purpose of versioning in migrations

   Version numbers or timestamps help keep track of the order in which changes are applied to the database.

2. Step 2: Recognize the benefit of ordered changes

   Applying changes in the correct order prevents conflicts and ensures the database schema updates safely.

3. Final Answer:

   To keep changes in the correct order and avoid conflicts -> Option A

4. Quick Check:

   Versioning = Order and safety [OK]

Hint: Version numbers keep changes in order to avoid conflicts [OK]

Common Mistakes:

• Thinking versioning speeds up the database
• Believing versioning reduces database size
• Assuming versioning hides changes from users

2. Which of the following is the correct way to name a migration file to ensure proper versioning?

easy

A. 001_create_users_table.sql

B. create_users_table.sql

C. users_table.sql

D. migration.sql

Solution

1. Step 1: Identify naming conventions for migrations

   Migrations should include a version number or timestamp prefix to keep them ordered.

2. Step 2: Compare options

   Only 001_create_users_table.sql uses a numeric prefix to version the migration file properly.

3. Final Answer:

   001_create_users_table.sql -> Option A

4. Quick Check:

   Number prefix = correct versioning [OK]

Hint: Use numbers or timestamps at start of migration file names [OK]

Common Mistakes:

• Omitting version numbers in file names
• Using generic names without order
• Naming files without clear versioning

3. Given these migration files applied in order: 001_init.sql, 002_add_email.sql, 003_update_password.sql. What happens if you try to apply 003_update_password.sql before 002_add_email.sql?

medium

A. The migration will apply successfully without issues

B. The database will automatically reorder the migrations

C. The migration will fail because the schema is not in the expected state

D. The migration will skip and do nothing

Solution

1. Step 1: Understand migration order importance

   Migrations must be applied in the correct order to keep the database schema consistent.

2. Step 2: Analyze applying migration 003 before 002

   Applying 003 before 002 means the database misses changes from 002, causing errors or failure.

3. Final Answer:

   The migration will fail because the schema is not in the expected state -> Option C

4. Quick Check:

   Out-of-order migration = failure [OK]

Hint: Always apply migrations in version order to avoid errors [OK]

Common Mistakes:

• Assuming migrations auto-reorder
• Thinking migrations can skip dependencies
• Believing migrations always succeed

4. You see this error when running migrations: ERROR: relation "users" does not exist. What is the most likely cause related to migration versioning?

medium

A. The database is full and cannot create new tables

B. A migration that creates the users table was not applied before this migration

C. The migration file has a syntax error

D. The users table was deleted manually after migration

Solution

1. Step 1: Understand the error meaning

   The error means the migration expects a users table that does not exist yet.

2. Step 2: Connect error to migration order

   If the migration creating the users table was not applied first, later migrations fail due to missing table.

3. Final Answer:

   A migration that creates the users table was not applied before this migration -> Option B

4. Quick Check:

   Missing prior migration = table not found error [OK]

Hint: Check if earlier migrations creating tables were applied [OK]

Common Mistakes:

• Blaming database storage issues
• Assuming syntax error without checking order
• Ignoring migration sequence

5. Your team is working on a Supabase project with multiple developers. Why is it important that migrations are versioned and shared in the project repository?

hard

A. To speed up the database performance during development

B. To allow each developer to create their own independent database schema

C. Because Supabase requires versioned migrations to run queries

D. So all developers apply database changes in the same order and avoid conflicts

Solution

1. Step 1: Understand team collaboration on database schema

   Multiple developers need to keep the database schema consistent to avoid conflicts.

2. Step 2: Role of versioned migrations in collaboration

   Versioned migrations shared in the repository ensure everyone applies changes in the same order safely.

3. Final Answer:

   So all developers apply database changes in the same order and avoid conflicts -> Option D

4. Quick Check:

   Shared versioned migrations = team sync [OK]

Hint: Share versioned migrations to keep team databases consistent [OK]

Common Mistakes:

• Thinking developers should have independent schemas
• Believing versioning is only for Supabase requirements
• Assuming versioning improves performance directly