prisma-cli

Run prisma migrate dev --name your_migration_name to create and apply a migration from schema changes. 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 or tracking history, making it suited for prototyping and MongoDB. migrate dev creates versioned migration files with drift detection and rollback capability, suited for team development.

Use prisma migrate deploy in production or CI/CD pipelines to apply pending migrations without prompts or a shadow database. Check prisma migrate status first, and never run migrate dev in production.

Prisma detects AI agent environments and blocks destructive commands like migrate reset and db push --force-reset until the user gives explicit consent. The agent must explain the data-loss impact and obtain consent immediately before running the command.

Yes, but you must run it with bunx --bun so Prisma uses the Bun runtime instead of falling back to Node.js due to the CLI shebang. This applies to commands like bunx --bun prisma init and bunx --bun prisma generate.

Run prisma db pull after configuring the datasource URL in prisma.config.ts to generate Prisma models from existing tables. Use --print to preview the schema before overwriting, then run prisma generate.