From 63a2c9db00fe62f4faa2e2aa3ecab501d970b5e1 Mon Sep 17 00:00:00 2001 From: Isaias Tavares Date: Wed, 4 Nov 2026 23:40:13 -0300 Subject: [PATCH] docs(db): drop a migration count and a planning reference from comments The baseline's count went stale with the first migration after the cut, and the lane test pointed at a document outside the repository. --- server/src/db/engine/postgres/baseline.ts | 2 +- server/tests/postgres/semantics.test.ts | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/server/src/db/engine/postgres/baseline.ts b/server/src/db/engine/postgres/baseline.ts index c5535bd12..32b619427 100644 --- a/server/src/db/engine/postgres/baseline.ts +++ b/server/src/db/engine/postgres/baseline.ts @@ -21,7 +21,7 @@ interface BaselineManifest { /** * The schema a fresh Postgres database starts from. * - * The 331 migrations up to `through` are written in SQLite and frozen, so a + * The migrations up to `through` are written in SQLite and frozen, so a * Postgres database does not replay them: it runs these statements, generated * from the entities (`npm run gen:pg-baseline`), and records every migration * in `migrations` as executed in the same transaction. Migrations after diff --git a/server/tests/postgres/semantics.test.ts b/server/tests/postgres/semantics.test.ts index 9ce770c25..f97094627 100644 --- a/server/tests/postgres/semantics.test.ts +++ b/server/tests/postgres/semantics.test.ts @@ -1,6 +1,6 @@ /** * PGSEM-001..002 — what SQLite gives for free and Postgres only through the - * engine (plan §5.4), against the real app on the lane's Postgres database: + * engine, against the real app on the lane's Postgres database: * writes in a UnitOfWork run one at a time, as on SQLite's single writer, so * a read-then-insert never races; counts come back as numbers; and a search * ignores case as SQLite's LIKE does.