The dump of a database that merges, and what is done with one. The mergeable tables (the version rows and the blobs) are the whole of what a dump carries: one INSERT for each row, the text the command sqlite3 x.db ".dump --data-only <tables>" writes. Replaying such a text into a database that has the layout (the schema is made first, since a dump has none) in one transaction adds the rows it does not hold and ignores the rest, so that the replay of any number of dumps, in any order, twice and overlapping, is the replay of their union: that is the merge. dumpText makes the dump in the same form, in key order; parseDump reads a dump as its rows and nothing else (the comments the command writes are skipped), and refuses any text that is anything but plain inserts of literals into the two tables, so that a dump is data and never a program; importDumps replays dumps through the store of the database (its trust stands in front of the rows) and then makes the index of search again and checks every row and blob.
What a replica that signs says of a dump it made: which replica made it, the SHA-256 of its text and how many rows and blobs it holds, in its key. A dump is data that anything can write, so under signed trust a dump is replayed only with a manifest whose signature holds; what is signed is the digest with the counts (<sha256>:<rows>:<blobs>) under the domain anyfs-dump/1, so that a signature of a delta or an epoch is never one of a dump. The file next to a dump is named <replica>.sql.sig.
The command that makes the dump of a database file with the real sqlite3: the data of the mergeable tables alone, as one INSERT for each row, and no schema.
The dump of a database as text, in key order: one INSERT for each version row and for each blob. A SQLite database gives it in the form the command makes (the engine's quote); any other engine gives the rows in its own form (see redump).
Replays dumps into the database of a store: the schema is there (the store made it), every dump is read as rows before anything is written (a text that is not a dump of plain inserts changes nothing), the rows are replayed in one transaction through the trigger that refuses a replica the database does not trust (and the whole replay is undone where one is refused), the index of search is made again, and every row and blob is checked.