How do you handle database schema migrations in a team environment?

Question

Two devs added columns to the same table in different branches. Both work individually but conflict when merged.

Interview OS Community · Accepted Answer

## Migration Best Practices

| Rule | Why |
|------|-----|
| Never edit committed migrations | Changes history for others |
| Pull main before creating | Reduces conflicts |
| Keep migrations small | Easier to review and revert |
| Add columns, don't modify | Backward compatible |

```bash
# Dev workflow
bunx prisma migrate dev --name add-salary-column
git pull --rebase origin main  # Sync first
bunx prisma migrate deploy     # Production: apply pending
```

## Safe patterns
```sql
-- ✅ Safe: Add nullable column (instant)
ALTER TABLE "Application" ADD COLUMN "notes" TEXT;
-- ⚠️ Dangerous: Changing type (rewrites table, locks)
```

Always backup before production migrations!

Loading Application

How do you handle database schema migrations in a team environment?

Question Details

Suggested Solution

Migration Best Practices

Dev workflow

Safe patterns

Discussion (0)