new-repository

Adding a new Drizzle schema table and SQLKit repository requires providing the entity name, table name, and fields to generate coordinated updates across schemas.ts, persistence-contracts.ts, domain-models.ts, and persistence-repositories.ts in your TypeScript project.

Creating a new SQLKit repository requires updating schemas.ts, persistence-contracts.ts, domain-models.ts, and persistence-repositories.ts. This cross-file coordination ensures the Drizzle schema and persistence layers remain synchronized across the TypeScript project.

After generating a Drizzle schema with bun, run database migrations by executing bun run db:generate followed by bun run db:push. This migration-ready workflow applies the newly generated schema changes directly to your database.

This repository generation workflow applies specifically to backend codebases using Drizzle ORM and SQLKit. Without an existing SQLKit setup, the coordinated updates to persistence contracts and repositories cannot be properly applied.

The best way to maintain cross-file consistency when adding a database entity is automating the generation of the Drizzle schema and SQLKit repository. This coordinates error-checked changes across schemas, contracts, models, and repositories simultaneously.

Drizzle schema migrations can fail after manually adding a table due to cross-file inconsistencies. Generating the schema and repository together ensures persistence-contracts.ts and domain-models.ts are properly aligned before running bun run db:generate.