database

Schema migrations are automated through a dual system of canonical SQL migrations and TypeScript runtime startup migrations, ensuring idempotency and traceability across development, staging, and production environments.

Idempotency is guaranteed by enforcing a clear migration orchestration order and an idempotency-first workflow, preventing schema drift and ensuring repeated migration applications yield the same result without breaking builds.

Yes, the dual migration system supports adding columns, creating tables, and modifying schemas safely. It uses a separate migrations folder and server startup migrations to apply changes across staging and production without breaking builds.

Yes, the system is designed as a dual migration framework, allowing both canonical Drizzle SQL migrations and TypeScript runtime startup scripts to apply schema changes safely and orchestrate updates.

To start applying schema changes, install or update the schema definitions in the shared/schema/ directory. Run the standard migration workflow to safely apply the updates on server startup.

A separate migrations folder is needed to maintain a reliable migration journal and clear naming conventions, preventing schema drift in dev and production while ensuring traceability during continuous deployment.