This page explains how Prisma uses migration histories to track changes to your schema.
Your migration history is the story of the changes to your data model, and is represented by:
prisma/migrationsfolder with a sub-folder and
migration.sqlfile for each migration:migrations/└─ 20210313140442_init/└─ migration.sql└─ 20210313140442_added_job_title/└─ migration.sql
migrationsfolder is the source of truth for the history of your data model.
_prisma_migrationstable in the database, which is used to check:
- If a migration was run against the database
- If an applied migration was deleted
- If an applied migration was changed
If you change or delete a migration (not recommended), the next steps depend on whether you are in a development environment (and therefore using
migrate dev) or a production / testing environment (and therefore using
In general, you should not edit or delete a migration that has already been applied. Doing so can lead to inconsistencies between development and production environment migration histories, which may have unforeseen consequences - even if the change does not appear to break anything at first.
The following scenario simulates a change that creates a seemingly harmless inconsistency:
Modify an existing migration that has already been applied in a development environment by changing the value of
VARCHAR(560):./prisma/migrations/20210310143435_default_value/migrations.sql1 -- AlterTable2 ALTER TABLE "Post" ALTER COLUMN "content" SET DATA TYPE VARCHAR(560);
After making this change, the end state of the migration history no longer matches the Prisma schema, which still has
prisma migrate dev- Prisma Migrate detects that a migration has changed, and asks to
resetthe database:? The migration `20210310143435_change_type` was modified after it was applied.We need to reset the PostgreSQL database "migrate-example" at "localhost:5432".Do you want to continue? All data will be lost. » (y/N)
If you accept resetting, Prisma Migrate resets the database and replays all migrations, including the migration you edited.
After applying all existing migrations, Prisma Migrate compares the end state of the migration history to the Prisma schema and detects a discrepancy:
- Prisma schema has
- Database schema has
- Prisma schema has
Prisma Migrate generates a new migration to change the value back to
550, because the end state of the migration history should match the Prisma schema.
From now on, when you use
prisma migrate deployto deploy migrations to production and test environments, Prisma Migrate will always warn you that migration histories do not match (and continue to warn you each time you run the command ) - even though the schema end states match:6 migrations found in prisma/migrationsWARNING The following migrations have been modified since they were applied:20210310143435_change_type
A change that does not appear to break anything after a
migrate reset can hide problems - you may end up with a bug in production that you cannot replicate in development, or the other way around - particularly if the change concerns a highly customized migration.
If Prisma Migrate reports a missing or edited migration that has already been applied, we recommend fixing the root cause (restoring the file or reverting the change) rather than resetting.
You must commit the entire
prisma/migrations folder to source control. This includes the
prisma/migrations/migration_lock.toml file, which is used to detect if you have attempted to change providers.
schema.prisma file is not enough - you must include your migration history. This is because:
- As you start to customize migrations, your migration history contains information that cannot be represented in the Prisma schema. For example, you can customize a migration to mitigate data loss that would be caused by a breaking change.
prisma migrate deploycommand, which is used to deploy changes to staging, testing, and production environments, only runs migration files. It does not use the Prisma schema file to fetch the models.