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 bunx --bun before Prisma commands, such as bunx --bun prisma init or bunx --bun prisma generate. Without the --bun flag, the CLI falls back to Node.js because of its shebang.

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.

No, migrate dev is for local development only because it prompts for input and uses a shadow database. In production or CI/CD, use prisma migrate deploy to apply pending migrations safely.

Run prisma dev to start a local PostgreSQL-compatible database in your terminal, or prisma dev --detach to run it in the background. Manage instances with prisma dev ls, stop, and rm commands.