Migraciones del esquema de la base de datos

As your application evolves, so does its database structure, also known as its schema.

Database migrations are like version control for your database schema. They are a way to manage changes to your database structure in a controlled and trackable manner.

• They ensure your database matches your application's needs.
• They prevent data loss during schema changes.
• They provide a clear history of all schema modifications.

Managing database schema changes manually can be complex and error-prone. Prisma Migrate simplifies this process significantly.

• Automatic Generation: It generates SQL migration files based on changes in your Prisma schema.
• History Tracking: It keeps a history of applied migrations, making rollbacks and team collaboration easier.
• Environment Consistency: Ensures your development, staging, and production databases all have the correct schema.

Prisma Migrate uses your schema.prisma file as the source of truth for your database schema. Any changes you want to make to your database structure start here.

Let's recall a basic schema.prisma setup:

When you first set up your Prisma schema, you'll want to create an initial migration to apply this schema to your database. You use the prisma migrate dev command for this.

This command does two main things:

1. Generates a new migration file (SQL) in the prisma/migrations folder.
2. Applies the migration to your database.

After running npx prisma migrate dev, Prisma creates a new folder inside prisma/migrations with a timestamp and the name you provided (e.g., 20231026123456_initial_setup).

Inside this folder, you'll find:

• migration.sql: This file contains the raw SQL commands generated by Prisma to create or alter your database tables.
• migration.js or migration.ts: (If using TypeScript/JavaScript) Metadata about the migration.

It's important to commit these files to your version control system!

Now, let's say you want to add an email field to your User model. You simply update your schema.prisma file.

Prisma will detect this change and help you generate a new migration.

After modifying your schema.prisma, run npx prisma migrate dev again. Prisma will compare your updated schema with the current database state and generate a new migration file.

It will then apply this new migration, adding the email column to your User table.

For production environments, you typically use npx prisma migrate deploy. This command applies all pending migrations that have not yet been run on the database.

Unlike migrate dev, deploy does not generate new migration files; it only applies existing ones. This makes it safe and predictable for production deployments.

To see which migrations have been applied to your database and which are pending, you can use the npx prisma migrate status command.

This is useful for debugging or ensuring your database is up-to-date with your application's expected schema.

Which of the following statements correctly describe the purpose of Prisma Migrate commands?

Great job! You've learned how to manage your database schema effectively using Prisma Migrate.

• Prisma Migrate helps version control your database schema.
• You define schema changes in schema.prisma.
• npx prisma migrate dev creates and applies migrations in development.
• npx prisma migrate deploy applies existing migrations in production.
• npx prisma migrate status checks the current migration state.

This powerful tool ensures your database structure stays consistent and aligned with your application's needs as it grows.