What changed in each release, why, and how to use it — with queries you can paste into a running server.
A driver transaction that committed on the spot, two writes of one unique value that both passed, and a custom role that granted nothing: what 2.1.0 fixes, plus database-limited roles, sync conflict resolution and OPTIONS on sharded collections.
Every collection used to be a RocksDB column family, and every create rewrote a file sized by the whole instance. 2.0 moves them into one shared keyspace: 10 creates went from 1,952 ms to 53 ms.
SoliDB 1.2.2 and 1.3.0 add date series, lookup maps, object diffs, accent folding, IBAN and SIRET checks, banker's rounding — and FOR now accepts any expression after IN.
SoliDB's rule is that a request may fail but never take the server down. A bulk UPSERT over @rows broke it: bind variables were copied once per row. How 1.2.3 fixed it.
One collection is one RocksDB column family, and each create or drop rewrites the whole OPTIONS file. 1.2.0 stops paying for that at startup, on delete-and-recreate, on listing, and on every WAL flush.
Until 1.1.0, RocksDB's block cache, table readers and memtables lived in glibc arenas that jemalloc's tuning never reached. What changed, the new per-component gauges in /metrics, and the knobs that bound memory.
1.1.0 puts SoliDB's own collections in three tiers behind one check, makes Lua scripts write as their caller, and gates the admin console. Each one closes a real finding; here is what a Write user now sees.
1.0.0 starts a fresh node closed (loopback, keyfile-only replication, authenticated /metrics), adds UNION/INTERSECT/EXCEPT, recursive CTEs and RETURN DISTINCT, and moves background jobs to Soli.
Before 0.34.0 a multi-machine cluster came up and replicated nothing. What was broken, --host vs --advertise, the now-mandatory keyfile, and a three-node setup on three machines.
In 0.33.0, FOR reads columnar collections like any other source, so FILTER, SORT, joins and subqueries work on them. Four aggregate bugs that returned wrong numbers instead of errors are also fixed.
0.33.0 adds POST /_api/backup, an instant RocksDB checkpoint of the whole instance, next to solidb-dump's portable JSONL. What each does, what it can't do, a decision table, and a runbook.