mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-11-20 02:56:10 +00:00
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.
This commit is contained in:
@@ -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
|
||||
|
||||
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user