0
0
Supabasecloud~10 mins

Rolling back migrations in Supabase - Interactive Code Practice

Choose your learning style9 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the command to rollback the last migration in Supabase CLI.

Supabase
supabase migration [1]
Drag options to blanks, or click blank then click option'
Aapply
Bstatus
Ccreate
Drollback
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'apply' instead of 'rollback' will apply migrations instead of undoing them.
Using 'create' is for making new migrations, not rolling back.
2fill in blank
medium

Complete the command to rollback migrations by specifying the number of steps.

Supabase
supabase migration rollback --steps [1]
Drag options to blanks, or click blank then click option'
Aall
B1
C0
D-1
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'all' is not valid for the steps option.
Using '0' means no rollback will happen.
3fill in blank
hard

Fix the error in the command to rollback migrations by adding the missing flag.

Supabase
supabase migration rollback [1] 2
Drag options to blanks, or click blank then click option'
A--steps
B--number
C--migrate
D--count
Attempts:
3 left
💡 Hint
Common Mistakes
Using '--count' or '--number' are not recognized flags for rollback steps.
Omitting the flag causes the command to fail.
4fill in blank
hard

Fill both blanks to rollback migrations and confirm the action automatically.

Supabase
supabase migration rollback [1] 1 [2]
Drag options to blanks, or click blank then click option'
A--steps
B--force
C--confirm
D--dry-run
Attempts:
3 left
💡 Hint
Common Mistakes
Using '--confirm' instead of '--force' does not skip prompts.
Using '--dry-run' only simulates rollback without applying it.
5fill in blank
hard

Fill all three blanks to rollback two migrations quietly and specify the project directory.

Supabase
supabase migration rollback [1] 2 [2] --project-dir [3]
Drag options to blanks, or click blank then click option'
A--steps
B--force
C./my-project
D--quiet
Attempts:
3 left
💡 Hint
Common Mistakes
Using '--quiet' instead of '--force' does not skip confirmation prompts.
Omitting the project directory causes the command to run in the current folder.