P3005

Shows how to fix error when creating new Prisma migration. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

Fixes the Prisma 'Drift detected: Your database schema is not in sync with your migration history' error by deciding whether the database or the migration history is the source of truth, then reconciling the two. Use when migrate dev refuse

Fixes Prisma error P3018 'A migration failed to apply' by deciding whether the failed migration's changes actually landed, then marking it rolled back or applied with migrate resolve. Use when migrate deploy stops with P3018 and new migrati

Fixes Prisma error P3005 'The database schema is not empty' during migrate deploy by baselining the existing database: mark the initial migration as already applied with migrate resolve --applied instead of letting migrate try to create tab