Squash migrations

How to squash prisma migrations

1. Backup your database. This step is critical. Don’t skip it.

Tip

You backup the db by using pgadmin or run the following command in your terminal

 pg_dump {dbname} > backup.sql

replace dbname with the name you called the database

2. Delete all contents in the “migrations” folder in your “prisma” directory.

Tip

This includes the migration_lock.toml file as it will be generated on the creation of a new migration.

3. Create a new empty directory in the “migrations” folder in your “prisma” directory called 000000000000_squashed_migrations. Inside this, add a new empty migration.sql.
4. Create a single migration that takes you:

• from an empty database
• to the current state of the production database schema as described in your ./prisma/schema.prismafile
• and outputs this to the migration.sql file created above

Tip

You can do this by using the migrate diff command. In terminal on the root directory, run the following command:

npx prisma migrate diff \
--from-empty \
--to-schema-datamodel ./prisma/schema \
--script > ./prisma/migrations/000000000000_squashed_migrations/migration.sql

5. Mark this migration as having been applied on production and dev, to prevent it from being run there by using the migrate resolve command. In terminal on the root directory, run the following command:

npx prisma migrate resolve \
--applied 000000000000_squashed_migrations

Tip

Remember to change DATABASE_URL variable in your local .env file to the appropriate remote database URL that can be found on clickup's BE/Important Resources page. If you are running Docker, you can run this in a terminal there.