Creating migrations in Supabase - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new migration with Supabase CLI.

Supabase

supabase [1] new add_users_table

Drag options to blanks, or click blank then click option'

Astart

Bmigration

Cmigrate

Dmigrations

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'migrate' instead of 'migration'.

Using plural 'migrations'.

The correct command to create a new migration is supabase migration new.

2fill in blank

medium

Complete the code to apply all pending migrations to the database.

Supabase

supabase [1] up

Drag options to blanks, or click blank then click option'

Amigrations

Bmigration

Cdeploy

Dmigrate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'migrations' plural instead of singular.

Using 'deploy' which is not a valid command here.

The command to apply migrations is supabase migrate up.

3fill in blank

hard

Fix the error in the command to rollback the last migration.

Supabase

supabase migration [1]

Drag options to blanks, or click blank then click option'

Adown

Brollback

Cundo

Drevert

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'undo' which is not a valid command.

Using 'rollback' or 'revert' which are not recognized.

The correct command to rollback the last migration is supabase migrate down.

4fill in blank

hard

Fill both blanks to create a migration file with a descriptive name and apply it.

Supabase

supabase [1] new [2] && supabase migration up

Drag options to blanks, or click blank then click option'

Amigration

Bmigrations

Cadd_orders_table

Dupdate_schema

Attempts:

3 left

💡 Hint

Common Mistakes

Using plural 'migrations' in the first blank.

Using a generic name instead of descriptive migration name.

Use supabase migration new add_orders_table to create the migration file, then apply it.

5fill in blank

hard

Fill all three blanks to create a migration, apply it, and check the migration status.

Supabase

supabase [1] new [2] && supabase migration [3]

Drag options to blanks, or click blank then click option'

Amigration

Badd_products_table

Cstatus

Dup

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'migrations' instead of 'migration' in the first blank.

Using 'up' instead of 'status' to check migrations.

Create the migration with migration new add_products_table, then check status with migration status.

Practice

1. What is the main purpose of creating migrations in Supabase?

easy

A. To save and track changes made to the database structure

B. To create user accounts automatically

C. To deploy frontend code to the server

D. To monitor server uptime and performance

Solution

1. Step 1: Understand what migrations do

   Migrations are files that record changes to the database schema over time.

2. Step 2: Identify the purpose in Supabase context

   Supabase uses migrations to save and track database structure changes so they can be applied consistently.

3. Final Answer:

   To save and track changes made to the database structure -> Option A

4. Quick Check:

   Migrations = track database changes [OK]

Hint: Migrations always track database structure changes [OK]

Common Mistakes:

• Confusing migrations with user management
• Thinking migrations deploy frontend code
• Assuming migrations monitor server health

2. Which command creates a new migration file in Supabase?

easy

A. supabase migration up

B. supabase db push

C. supabase migration new

D. supabase start migration

Solution

1. Step 1: Recall Supabase migration commands

   The command to create a new migration file is specifically designed to generate the file for changes.

2. Step 2: Match command to action

   supabase migration new creates a new migration file, while others apply or push changes.

3. Final Answer:

   supabase migration new -> Option C

4. Quick Check:

   Create migration file = supabase migration new [OK]

Hint: New migration files use 'migration new' command [OK]

Common Mistakes:

• Using 'db push' to create migration files
• Confusing 'migration up' with creation
• Typing incorrect commands like 'start migration'

3. After creating a migration file, which command applies the changes to your remote database?

medium

A. supabase migration up

B. supabase db push

C. supabase migration new

D. supabase db pull

Solution

1. Step 1: Understand commands for applying migrations

   supabase db push applies schema changes to the remote database by pushing local migrations.

2. Step 2: Differentiate commands

   supabase migration up applies migrations locally, while supabase db push pushes changes remotely.

3. Final Answer:

   supabase db push -> Option B

4. Quick Check:

   Apply remotely = db push [OK]

Hint: Use 'supabase db push' to apply migrations remotely [OK]

Common Mistakes:

• Using 'supabase migration up' to apply migrations remotely
• Confusing 'migration new' as apply command
• Thinking 'db pull' applies migrations

4. You ran supabase migration up but got an error saying migrations are missing. What is the likely cause?

medium

A. You used the wrong command to apply locally

B. You need to restart the Supabase server

C. Your database connection is offline

D. You forgot to create migration files before applying

Solution

1. Step 1: Analyze the error about missing migrations

   The error indicates no migration files exist to apply locally.

2. Step 2: Identify the cause

   This usually happens if migration files were never created with supabase migration new.

3. Final Answer:

   You forgot to create migration files before applying -> Option D

4. Quick Check:

   Missing migrations = no files created [OK]

Hint: Create migration files before applying locally [OK]

Common Mistakes:

• Assuming connection issues cause missing migrations
• Restarting server without creating files
• Confusing local and remote apply commands

5. You want to update your remote Supabase database with new schema changes. Which sequence of commands should you run?

hard

A. supabase migration new -> supabase start -> supabase migration up

B. supabase db push -> supabase migration new -> supabase migration up

C. supabase migration up -> supabase migration new -> supabase db push

D. supabase migration new -> supabase migration up -> supabase db push

Solution

1. Step 1: Create migration files first

   Use supabase migration new to save schema changes as migration files.

2. Step 2: Apply changes locally

   Run supabase start to update your local database with these changes.

3. Step 3: Apply migrations remotely

   Finally, run supabase migration up to update the remote database.

4. Final Answer:

   supabase migration new -> supabase start -> supabase migration up -> Option A

5. Quick Check:

   Create -> local start -> remote up [OK]

Hint: Create migration, start locally, then up remotely [OK]

Common Mistakes:

• Applying migrations before creating files
• Applying remotely before local test
• Mixing order of commands