Prisma migrations in NestJS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of Prisma migrations in a NestJS project?

Prisma migrations help manage and apply changes to the database schema in a safe and organized way. They keep the database structure in sync with your Prisma schema file.

beginner

Which command creates a new migration file after updating the Prisma schema?

The command npx prisma migrate dev --name your_migration_name creates a new migration file and applies it to the database during development.

intermediate

How does Prisma ensure migrations are applied in the correct order?

Prisma stores migration history in a special table in the database. It applies migrations sequentially based on this history to keep the database consistent.

intermediate

What should you do before running migrations in a production environment?

You should review migration files carefully, back up your database, and run npx prisma migrate deploy to apply migrations safely without prompts.

beginner

Why is it important to commit migration files to version control?

Committing migration files lets your team share database changes and ensures everyone applies the same schema updates, avoiding conflicts and errors.

Which Prisma command applies migrations during development and updates the database?

A npx prisma generate

B npx prisma migrate dev --name migration_name

C npx prisma studio

D npx prisma migrate deploy

The migrate dev command creates and applies migrations during development.

Where does Prisma store the migration history to track applied migrations?

A In a special table inside the database

B In the Prisma schema file

C In a JSON file in the project root

D In environment variables

Prisma uses a dedicated table in the database to track migration history.

What is the recommended command to apply migrations in a production environment?

A npx prisma migrate reset

B npx prisma migrate dev

C npx prisma migrate deploy

D npx prisma generate

The migrate deploy command applies migrations safely in production.

Why should migration files be committed to version control?

A To share schema changes with the team

B To speed up the application runtime

C To store database credentials

D To generate Prisma client

Committing migration files helps the team stay in sync with database changes.

What happens if you change the Prisma schema but do not create a migration?

A The Prisma client will update automatically

B The database will reset

C The migration will be created automatically on app start

D The database schema will not update

Without creating a migration, the database schema stays unchanged.

Explain the steps to create and apply a new Prisma migration in a NestJS project.

Think about how you change the schema and then update the database safely.

Describe how Prisma migrations help keep your database consistent across different environments.

Consider how migrations track and share changes to avoid conflicts.