prisma-cli

Run prisma migrate dev --name your_migration_name to generate and apply a migration from schema changes. It uses a shadow database for drift detection, and you should run prisma generate afterward to refresh the client output.

db push syncs the schema directly without creating migration files or tracking history, making it ideal for prototyping and MongoDB. migrate dev creates versioned migration files with rollback capability, suited for team development and production paths.

Use prisma migrate deploy, which applies pending migrations without prompts, drift detection, or a shadow database. Check prisma migrate status first, and never run migrate dev in production environments.

Yes, but you must add the --bun flag, for example bunx --bun prisma generate. Without it, the CLI falls back to Node.js because of its shebang, which can cause runtime mismatches in Bun projects.

Resolve the underlying issue, then run prisma migrate resolve --rolled-back <migration_name> to mark it as failed, or --applied to baseline it. After resolving, re-run prisma migrate deploy to continue applying migrations.

Avoid db push in production, in team environments needing trackable changes, and whenever rollback capability matters, since it creates no migration history. Use migrate dev and migrate deploy for those scenarios instead.