prisma-cli

Run prisma migrate dev --name your_migration_name to create and apply a migration during development. It uses a shadow database to detect drift, generates SQL files in prisma/migrations, and applies them to your development database.

db push syncs schema changes directly without creating migration files or tracking history, making it faster for prototyping. migrate dev creates versioned migration files with rollback capability, making it the right choice for team collaboration and production-bound work.

Yes, but you must add the --bun flag when running commands via bunx, such as bunx --bun prisma generate. Without it, the CLI falls back to Node.js because of its shebang.

Use prisma migrate resolve --rolled-back <migration_name> to mark the failed migration as rolled back, fix the underlying SQL or database issue, then re-run prisma migrate deploy. Check prisma migrate status first to confirm the failure.

Avoid db push in production environments, team workflows requiring trackable changes, and any scenario needing rollback capability. Use migrate dev and migrate deploy instead, since db push creates no migration history.