​
Database Migrations

Manage database schema changes with Prisma migrations.

​
Development Workflow

​
Quick Sync (db push)

For rapid development, use db:push to sync schema without migrations: 
bun run db:push
db:push is for development only. It may cause data loss. Use migrations for production.

​
Create Migration

Create a migration file for production: 
bun run db:migrate
This will:
  1. Generate SQL migration files
  2. Apply pending migrations
  3. Regenerate Prisma Client

​
Migration Files

Migrations are stored in packages/database/prisma/migrations/: 
prisma/migrations/
├── 20240101000000_init/
│   └── migration.sql
├── 20240115000000_add_posts/
│   └── migration.sql
└── migration_lock.toml

​
Common Workflows

​
Adding a New Field

  1. Update schema.prisma:
model User {
  // ... existing fields
  bio String?  // New field
}
  1. Create migration:
bun run db:migrate
  1. Name your migration: add_user_bio

​
Renaming a Field

  1. Update schema
  2. Create migration with --create-only:
cd packages/database
npx prisma migrate dev --create-only
  1. Edit the migration SQL to use RENAME COLUMN
  2. Apply: npx prisma migrate dev

​
Reset Database

Reset development database (deletes all data): 
cd packages/database
npx prisma migrate reset

​
Production Deployment

Deploy migrations in production: 
npx prisma migrate deploy
Always backup your production database before running migrations.