database ยท diff
git:20261031.60324e5 to git:20261107.b47c639
1 added, 1 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
---
name: database
- description: Use when changing database schemas, migrations, database access, or database package structure. Keeps the Drizzle schema authoritative and migrations generated.
+ description: Use when changing database schemas, migrations, database access, or database package structure.
---
# Database and migrations
Databases default to Drizzle, and the Drizzle schema is the source of truth. Generate migrations from it with `drizzle-kit generate`, and use `drizzle-kit generate --custom` for SQL the schema can't express.
Unless a database is private to one app, its schema, migrations, Drizzle config, and scripts live in a dedicated package: `packages/db` for the primary database, and one package per additional database.
Effect code accesses PostgreSQL through `@effect/sql-pg`, using the connection helpers from the project's `@<project>/db` package rather than its own `PgClient`.
When a process opens more than one pool against the same database, such as an Effect client beside the `pg` pool an auth library uses, their maximum sizes together stay within the role's connection limit in every environment, including pull request previews. Pools can't lend each other idle connections, and a query past a full pool waits while one past the role's limit fails. An integration test saturates every pool at once against a role created with that limit.
The canonical justfile owns the local development database (`just dev-db-start`). Don't add a project script or compose file for it.
`bun run` doesn't load `.env.local`, so scripts that need `DATABASE_URL` load it explicitly, as in `"db:migrate": "bun --env-file=.env.local drizzle-kit migrate"`.