db-migrate

To generate a safe Postgres migration, modify your Drizzle schema and use this process to inspect the generated SQL, catching risky changes like unintended drops or rename mishandling before execution. It validates changes to prevent data loss.

The safest way to add a column is applying a controlled schema edit, generating a Drizzle migration, and verifying the SQL output for risky operations. This workflow prevents production data loss when introducing new nullable or required fields.

Drizzle handles enum changes by guiding the schema edit and validating the generated Postgres migration SQL. This controlled workflow catches unsafe modifications, ensuring enum changes in production databases do not cause unintended data loss.

Yes, you can use this workflow to add indexes and relations to an existing Postgres schema. It safely modifies the Drizzle schema, generates a validated migration, verifies the SQL, and updates documentation to align with the live database.

You should verify generated SQL before running a Drizzle schema migration to catch risky changes like unintended table drops or rename mishandling. This verification step is critical to prevent irreversible data loss in production database workflows.

You do not need to manually update database documentation after generating a Drizzle migration. The workflow includes a documentation sync step to keep your schema docs aligned with the live Postgres database after changes are applied.