prisma-cli

Run prisma migrate dev --name your_migration_name to create 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 history, making it ideal for prototyping and MongoDB. migrate dev creates tracked migration files with rollback capability and is the correct choice for team development and production-bound changes.

Use prisma migrate deploy in production, staging, and CI/CD pipelines. It applies pending migrations without prompts or a shadow database, and you should run prisma migrate status first to verify the database state.

Yes, but you must run commands with bunx --bun, for example bunx --bun prisma generate. Without the --bun flag, the CLI falls back to Node.js because of its shebang.

In current Prisma 7.x behavior, migrate dev does not reliably emit generated client files even though CLI help text suggests it triggers generators. Run prisma generate explicitly after migrate dev, db push, or migrate reset when you need fresh client output.

Avoid db push in production, in team environments needing trackable changes, and whenever you need rollback capability. Use migrate dev and migrate deploy instead, since db push creates no migration history.