Simon Frei 4459438245 chore(db): update schema version in the same transaction as migration (#10321) ...

Just to be entirely sure that if the migration succeeds the schema
version is always also updated. Currently if a migration succeeds but a
later migration doesn't, the changes of the migration apply but the
version stays - if the migration is breaking/non-idempotent, it will
fail when it tries to rerun it next time (otherwise it's just a
pointless re-execution).

Unfortunately with the current `db.runScripts` it wasn't that easy to
do, so I had to do quite a bit of refactoring. I am also ensuring the
right order of transactions now, though I assume that was already the
case lexicographically - can't hurt to be safe.

2025-08-30 13:18:31 +02:00

..

blob

chore: add missing copyright in new files from infra branch (#10055)

2025-04-13 09:25:16 +00:00

db

chore(db): update schema version in the same transaction as migration (#10321)

2025-08-30 13:18:31 +02:00

gen

chore(protocol): minor cleanup of ClusterConfig messages; remove DisableTempIndexes option (#10202)

2025-06-29 10:18:51 +02:00

itererr

chore: switch database engine to sqlite (fixes #9954) (#9965)

2025-03-29 13:50:08 +01:00

protoutil

chore(internal): linter complaints

2025-06-06 13:45:44 +02:00

slogutil

chore(slog): re-enable LOGGER_DISCARD (fixes #10262) (#10267)

2025-08-19 22:36:10 +02:00

timeutil

chore: switch database engine to sqlite (fixes #9954) (#9965)

2025-03-29 13:50:08 +01:00