prisma-cli

Run prisma migrate dev --name your_migration_name to create and apply a migration during development. Afterwards, run prisma generate explicitly to refresh the client and prisma db seed if you need seed data.

db push syncs the schema directly without creating migration files, making it faster for prototyping. migrate dev creates tracked migration files with history and rollback capability, which is better for team collaboration and production paths.

Use bunx --bun before the command, 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, you should run prisma generate explicitly after migrate dev when you need refreshed client output. The same applies to running prisma db seed explicitly after migrations or resets.

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 migrate status first to inspect the current state.

Avoid db push in production, in team environments needing trackable changes, and when you need rollback capability. Use migrate dev and migrate deploy instead for those scenarios.