Database Migration

Safe SQL migrations require using IF NOT EXISTS patterns and avoiding subtransaction issues to ensure repeatable database upgrades. This approach codifies those rules to prevent common errors when adding enums, tables, or indexes.

Adding enum values safely during a database migration involves using idempotent SQL patterns within your migration files to prevent conflicts. This skill automates the integration of these enum changes alongside Prisma schema updates.

The best way to integrate Prisma migrations with hand-written SQL is to update the Prisma schema first, then add a matching idempotent SQL migration file under your backend's prisma/migrations directory before deploying.

Hand-written database migrations fail due to subtransaction issues when SQL statements trigger implicit transactions that conflict with migration execution rules. This skill enforces specific patterns to avoid these pitfalls during schema changes.

To deploy idempotent schema changes using Prisma, update your schema, add a matching SQL migration file using IF NOT EXISTS patterns, then run Prisma generate and deploy to apply the changes safely to your database.