k1nq/TREK
1
0
Fork 0
mirror of https://github.com/mauriceboe/TREK.git synced 2026-10-18 21:16:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(server): say which builds refuse a migrated database and which do not

Browse Source 
The pre-migrate snapshot docstring said an older release refuses a database a newer TREK migrated. Only images from 5.0 on do; 4.3.x and earlier start on it without a warning. server/CLAUDE.md said anything the legacy baseline cannot map refuses the boot, which holds only above step 258.
This commit is contained in:
Maurice
2026-10-13 21:10:41 +02:00
parent 6694a38e65
commit bf26175724
2 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
server/CLAUDE.md
+1 -1
View File
File diff suppressed because one or more lines are too long
server/src/db/pre-migrate-snapshot.ts
+6 -4
View File
@@ -8,10 +8,12 @@ import path from 'node:path';
/**
* A copy of the database taken right before a boot migrates it.
*
* Migrations only go forward, and a database a newer TREK migrated is refused
* by the older one (`refuseNewerDatabase`). Without a copy from before the
* upgrade, going back to the previous image means restoring a backup, and
* automatic backups are off by default. So the boot takes one itself: a
* Migrations only go forward. An image from 5.0 on refuses a database a newer
* TREK migrated (`refuseNewerDatabase`), but 4.3.x and earlier do not check:
* they start on the newer schema without a warning and run on what they
* understand of it. Either way, going back to the previous image means going
* back to a copy from before the upgrade, and automatic backups are off by
* default. So the boot takes one itself: a
* `VACUUM INTO` snapshot next to the database file, named after the schema it
* holds, e.g. `pre-migrate-legacy-244-20261008T091500Z.db` for a v4.3.3
* install or `pre-migrate-20200101042300-….db` for one the migrator already