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 tracking history, making it ideal for prototyping and MongoDB. migrate dev creates versioned migration files with rollback capability and is the right choice for team development.

Use bunx --bun before Prisma commands, such as bunx --bun prisma init or bunx --bun prisma generate. Without the --bun flag, Prisma falls back to Node.js because of the CLI shebang.

No, in current Prisma versions you must run prisma generate and prisma db seed explicitly after migrate dev when you need refreshed client output or seed data. Configure the seed command in prisma.config.ts under migrations.seed.

Resolve the underlying issue, then run prisma migrate resolve --rolled-back <migration_name> to mark it as rolled back, and re-run prisma migrate deploy. Use --applied instead when baselining an existing database.

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