safe-migration

Safe Prisma migrations require enforcing `migrate dev` over `db push`, verifying database backups with explicit user confirmation, and identifying potentially destructive SQL operations before execution to prevent data loss.

Using `migrate dev` instead of `db push` ensures schema changes generate trackable migration history. It enforces systematic updates and validates changes against specifications, preventing accidental data corruption that `db push` might cause.

Validate Prisma schema changes against project specifications by checking modifications against defined documentation like `specs/multi-vendor-ecommerce/03-data-model.md` to ensure structural consistency and compliance before applying migrations.

Prisma migration processes can identify and warn about potentially destructive SQL operations such as DROP, DELETE, and ALTER DROP before execution, requiring explicit user confirmation to prevent accidental data loss.

After a Prisma database migration, update server actions, types, schemas, and documentation. The migration process suggests necessary code modifications to keep the codebase consistent with the new database schema.

Using `db push` for schema updates is prohibited in safe migration workflows. You must use `migrate dev` to ensure all schema changes are tracked, validated against specifications, and applied systematically.