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 explicitly afterward to refresh the client.

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

Use prisma migrate deploy, which applies pending migrations without prompts or shadow databases, making it safe for CI/CD pipelines. Check prisma migrate status first and never run migrate dev in production.

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 the CLI shebang.

In Prisma 7.6.0, migrate dev does not reliably emit generated client files despite CLI help text suggesting it triggers generators. Run prisma generate explicitly after schema-changing commands when you need fresh client output.

Avoid db push in production, in team collaboration requiring trackable changes, and when you need rollback capability. Use migrate dev and migrate deploy instead for versioned, recoverable schema changes.