docs(db): describe the move's refusals and --drop-nul

The wiki's move section, the server guide and the nul-free header said
the move drops NUL as every write does. They now say what it does: a
plugin's data moves unchanged or the move is refused with the values
listed, TREK's own NUL is refused unless --drop-nul is given, which lists
every value it changed, and the checksum comes from the SQLite values.
This commit is contained in:
Maurice
2026-11-17 23:28:11 +01:00
parent 621b2f17df
commit c75fb22289
3 changed files with 23 additions and 10 deletions
+3 -1
View File
@@ -22,7 +22,9 @@ import type { AbortableOperationOptions, CompiledQuery, DatabaseConnection, Dial
* through {@link withNulFreeParameters}, which covers the Kysely
* statements of the repositories;
* - the move from SQLite to Postgres (`engine/postgres/sqlite-move/values.ts`)
* copies text the same way.
* drops it from TREK's own text only when the operator asks for it
* (`--drop-nul`) and lists each value it changed; by default it refuses
* such a value, since the move changes nothing silently.
*
* A plugin's own data (`db:own`) is not TREK's to change: its SQLite file
* (`nest/plugins/host/plugin-data.service.ts`) binds a NUL exactly, so keys