bermudalambandClaude Opus 5
e7fd63c2e6
Infrastructure only. No route is converted, nothing changes at run time. The mirror had already drifted, which settles how it should be maintained. schema.ts was missing item_drafts and upload_links from the moment #222 landed, because the spike pulled into ./drizzle and copied the file into src/ by hand, and nobody had reason to look at the copy for a week. So `out` now points at src/db-drizzle and pull refreshes in place — the copy step that made the drift possible is gone — and tablesFilter excludes pgmigrations, which is node-pg-migrate's bookkeeping and has no business in a model of the application's schema. A stale mirror is worse than no mirror, because Drizzle infers row types from it: a converted query would type-check against a schema the database does not have and fail at run time on a column that does not exist. drizzleSchema.integration.test.ts fails when the two disagree, on tables and on columns. It was checked by removing item_drafts from the mirror and confirming the test fails naming it, rather than trusting a green run on a file that already matched. pull also emits 0000_*.sql and meta/ into `out`, because that directory serves both purposes. Both are gitignored: this project's migration history is backend/migrations, hand-written and mostly prose, and #219 has not chosen otherwise — a stray SQL file in src/ is at best noise and at worst mistaken for real history. db is exported beside pool and shares its connections. Both must work at once, since conversion is file by file across 187 sites; separate pools would make a transaction on one invisible to the other and silently double the configured limits. The generated files are excluded from linting. #261 hand-fixed an unused-parameter warning in schema.ts and this re-pull put it straight back, which is the argument in one line: linting generated code buys a fix the next regeneration undoes. itemFilters.drizzle.ts, which is hand-written, is still linted. CONVENTIONS.md records the sql.param() array trap before anyone hits it — the wrong form type-checks, reads correctly and fails at run time as invalid Postgres — and the reason the adoption is worth doing at all, which is that ${value} emits a bind parameter and there is no way to spell "interpolate this as SQL" by accident. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
32 lines
1.4 KiB
TypeScript
32 lines
1.4 KiB
TypeScript
import { defineConfig } from 'drizzle-kit';
|
|
|
|
// Spike configuration (#216). Credentials come from the environment rather than
|
|
// this file — the same rule the rest of the repo follows, and this one points at
|
|
// a developer's local database, not a deployed one.
|
|
//
|
|
// DRIZZLE_DATABASE_URL=postgres://redefined_local:redefined_local@localhost:55500/redefined_local
|
|
export default defineConfig({
|
|
dialect: 'postgresql',
|
|
schema: './src/db-drizzle/schema.ts',
|
|
|
|
// `drizzle-kit pull` writes its output here, so this points at the directory
|
|
// the application actually imports from. The spike pulled into ./drizzle and
|
|
// copied the file into src/ by hand, and that copy drifted exactly as
|
|
// predicted — not because anyone re-pulled, but because #222 added
|
|
// item_drafts and upload_links and the mirror was never refreshed. Nothing
|
|
// noticed for a week. Pulling in place removes the copy step that made that
|
|
// possible. See #217.
|
|
//
|
|
// If #219 ever chooses generated migrations, they also land in `out`, and
|
|
// this will need splitting then. It is a queries-only mirror today.
|
|
out: './src/db-drizzle',
|
|
|
|
// pgmigrations is node-pg-migrate's own bookkeeping. It is not part of the
|
|
// application's schema and has no business in a generated model of it.
|
|
tablesFilter: ['!pgmigrations'],
|
|
|
|
dbCredentials: {
|
|
url: process.env.DRIZZLE_DATABASE_URL ?? ''
|
|
}
|
|
});
|