Migration Modified After Applied (but checksums are the same)

I have not ad any issues with my procedures yet, but today when I went to modify my chema and generate a new migration, I got the following

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQL Server database

- The migration `20241016154659_feature_flags_uq_fk` was modified after it was applied.
- The migration `20241024155043_fk_survey_request_resends` was modified after it was applied.

We need to reset the database schema

You may use prisma migrate reset to drop the development database.

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQL Server database

- The migration `20241016154659_feature_flags_uq_fk` was modified after it was applied.
- The migration `20241024155043_fk_survey_request_resends` was modified after it was applied.

We need to reset the database schema

You may use prisma migrate reset to drop the development database.

However, these are migrations that have been run a long time ago. I verified the checksum of my migration.sql files and the value stored in the db. They are the same. How do I get past this?

Prisma•12mo ago•

13 replies

jermahs

Migration Modified After Applied (but checksums are the same)

I have not ad any issues with my procedures yet, but today when I went to modify my chema and generate a new migration, I got the following

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQL Server database

- The migration `20241016154659_feature_flags_uq_fk` was modified after it was applied.
- The migration `20241024155043_fk_survey_request_resends` was modified after it was applied.

We need to reset the database schema

You may use prisma migrate reset to drop the development database.

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQL Server database

- The migration `20241016154659_feature_flags_uq_fk` was modified after it was applied.
- The migration `20241024155043_fk_survey_request_resends` was modified after it was applied.

We need to reset the database schema

You may use prisma migrate reset to drop the development database.

However, these are migrations that have been run a long time ago. I verified the checksum of my migration.sql files and the value stored in the db. They are the same. How do I get past this?

Migration Modified After Applied (but checksums are the same)

Similar Threads

Migration Modified After Applied (but checksums are the same)

Similar Threads

Similar Threads

Similar Threads