Db Migration

3. Generate and review the migration

cd ufc-news-hub
npx prisma migrate dev --name descricao_da_mudanca

• Review the generated SQL in prisma/migrations/
• Verify it won't drop data or break constraints

4. Regenerate the Prisma client

cd ufc-news-hub
npx prisma generate

5. Update raw SQL queries

Search for affected tables/columns in raw SQL:

grep -rn "nome_da_tabela\|nome_da_coluna" src/ --include="*.ts"

Update all query() and queryOne() calls to match new schema.

6. Update TypeScript types

• Check src/types/ for affected type definitions
• Update interfaces to match new schema

7. Verify everything

cd ufc-news-hub
npx prisma generate       # Regenerate client
npm run lint              # Lint check
npx tsc --noEmit          # Type check
npm run build             # Build check

8. Test data integrity

-- Run against local DB to verify migration
SELECT COUNT(*) FROM nova_tabela;
SELECT * FROM tabela_modificada LIMIT 5;

Safety Rules

• NEVER drop columns/tables without confirming with the user
• NEVER modify existing migrations that are already committed
• ALWAYS back up data before destructive migrations: pg_dump
• ALWAYS update BOTH raw SQL queries AND Prisma usage
• For production: use npx prisma migrate deploy (not dev)

Common Table Names Reference