Creating migrations in Supabase - Practice Exercises

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens when you run supabase db push with no new migration files?

You have an existing Supabase project with migrations applied. You run the command supabase db push but have not added any new migration files. What is the expected behavior?

A The command detects no new migrations and makes no changes to the database schema.

B The command applies all existing migrations again, duplicating schema changes.

C The command deletes all existing tables and recreates them from scratch.

D The command throws an error indicating no migration files found.

💡 Hint

Think about what happens if there is nothing new to apply.

The supabase db push command only applies new migration files that have not yet been applied. If there are no new migrations, it does nothing and leaves the database schema unchanged.

❓ Configuration

intermediate

Which file must be updated to configure the database connection for Supabase migrations?

To run migrations with Supabase CLI, you need to specify the database connection details. Which configuration file is used to set the connection string for migrations?

A supabase/config.toml

B supabase/.dbconfig

C supabase/migrations.yaml

D .env

💡 Hint

Supabase uses environment variables for sensitive info.

The .env file holds environment variables including the database connection string used by Supabase CLI for migrations.

❓ Architecture

advanced

What is the best practice for organizing migration files in a Supabase project?

Consider a Supabase project with multiple developers working on database schema changes. How should migration files be organized to avoid conflicts and ensure smooth deployment?

A Each developer keeps migration files locally and runs them manually without sharing.

B Store all migration files in a single folder with timestamped filenames and commit them to version control.

C Use a single migration file for all changes and overwrite it for every update.

D Store migration files outside the project folder to avoid accidental commits.

💡 Hint

Think about collaboration and version control.

Best practice is to keep migration files in a dedicated folder with clear timestamps or version numbers, and commit them to version control so all developers share the same schema history.

❓ security

advanced

Which practice improves security when managing Supabase migration files?

When handling migration files that include sensitive schema changes, which practice helps protect sensitive information?

A Avoid including sensitive data like passwords or secrets directly in migration files.

B Store migration files in a public repository for transparency.

C Include database credentials inside migration SQL scripts for automation.

D Encrypt migration files before committing to version control.

💡 Hint

Think about what should never be in code files.

Migration files should never contain sensitive information such as passwords or secrets. These should be managed separately via environment variables or secret management tools.

🧠 Conceptual

expert

What is the effect of running supabase db reset in a project with existing migrations?

You run supabase db reset in your project directory. What happens to your database and migration files?

A Migration files are deleted but the database remains unchanged.

B Only the last migration is applied to the existing database without dropping it.

C The database is dropped and recreated, then all migrations are reapplied from the first to last.

D The command only clears the migration history without affecting the database schema.

💡 Hint

Consider what 'reset' usually means for a database.

The supabase db reset command drops the current database, recreates it fresh, and then reapplies all migration files in order to rebuild the schema from scratch.