drizzle-migration

Database migrations are generated automatically from TypeScript schema changes using Drizzle Kit. Run `bun run db:generate` after modifying your schema files in `packages/asset-forge/server/db/schema` to create SQL migration files that Drizzle Kit outputs to your migrations directory.

Yes, Drizzle Kit migrations work with both PostgreSQL and SQLite. The schema changes you define in TypeScript compile to compatible SQL for either database, controlled by your Drizzle Kit configuration and the DATABASE_URL in your .env file.

Before applying migrations, review the generated SQL for correctness and unintended changes using a checklist: verify column modifications, constraint changes, and data transformations. Apply migrations to development first via `bun run db:migrate`, then verify results in Drizzle Studio before promoting to production.

Apply migrations using `bun run db:migrate` with DATABASE_URL configured in your .env file. This executes pending migration files against your database in order, updating your schema and maintaining a migration history for rollback and auditing.

If schema changes aren't migrated, your TypeScript schema definition diverges from your actual database state, causing runtime errors or data inconsistencies. Always run `bun run db:generate` after schema modifications to keep migrations in sync with your code.

Drizzle Kit supports schema evolution including adding fields, modifying columns, and managing constraints through TypeScript schema definitions. For the asset-forge project, it automates migration generation from schema changes, though complex transformations require reviewing and potentially editing generated SQL manually.