How to fix P3017: The migration could not be found in Prisma

# Check migration status to see which migration is problematic
npx prisma migrate status

# Or query the migrations table directly
npx prisma db execute --stdin --schema=./prisma/schema.prisma << 'EOF'
SELECT "migration_name", "applied_at", "finished_at"
FROM _prisma_migrations
WHERE "finished_at" IS NOT NULL
ORDER BY "applied_at" DESC;
EOF

# List all migration files
ls -la prisma/migrations/

# Look for the specific migration mentioned in the error
# For example, if error mentions "20250101120000_add_users_table":
find prisma/migrations/ -name "*20250101120000*" -type d

# Check file permissions
ls -la prisma/migrations/[TIMESTAMP]_migration_name/

# Check if migration.sql exists
ls -la prisma/migrations/[TIMESTAMP]_migration_name/migration.sql

# Check file size
wc -l prisma/migrations/[TIMESTAMP]_migration_name/migration.sql

# Check Git history for the missing migration
git log --oneline -- prisma/migrations/

# Restore specific migration from Git
git checkout [commit-hash] -- prisma/migrations/[TIMESTAMP]_migration_name/

npx prisma db execute --stdin --schema=./prisma/schema.prisma << 'EOF'
UPDATE _prisma_migrations
SET "rolled_back_at" = NOW(),
    "logs" = 'Manually rolled back due to missing migration file (P3017)'
WHERE "migration_name" = '[missing_migration_name]';
EOF

npx prisma db execute --stdin --schema=./prisma/schema.prisma << 'EOF'
DELETE FROM _prisma_migrations
WHERE "migration_name" = '[missing_migration_name]'
  AND "finished_at" IS NULL;
EOF

# First, backup your database
pg_dump your_database > backup_before_reset.sql

# Reset migrations (this will clear all migration history)
npx prisma migrate reset

# Or manually:
npx prisma db execute --stdin --schema=./prisma/schema.prisma << 'EOF'
TRUNCATE TABLE _prisma_migrations;
EOF

# Check migration status
npx prisma migrate status

# Should show all migrations as either "Success" or pending
# No more P3017 errors should appear

# Test creating a new migration
npx prisma migrate dev --name test_after_p3017_fix

# Verify the new migration applies successfully
npx prisma migrate deploy --preview-feature

# Ensure migrations directory is tracked
git add prisma/migrations/
git commit -m "Add migration files"

# DO NOT ignore migration files
# prisma/migrations/ should be committed
!prisma/migrations/

# Regular backups of migration directory
tar -czf migrations_backup_$(date +%Y%m%d).tar.gz prisma/migrations/

# In your CI pipeline
- name: Verify migration files
  run: |
    npx prisma migrate status
    # Should not show any P3017 errors