redb 3.6.0

[reliktbk]

redb 3.6.0 is out. Two correctness fixes in the core, one of which was silently returning rows from the wrong tree, plus a rebuilt SQLite native extension.

Highlights

Root-scoped tree queries no longer scan the whole scheme. TreeQuery(root).WhereLeaves() and .WhereRoots() built their query from _id_scheme alone and dropped the root, so a root-scoped query returned the leaves or roots of every tree in the scheme. If you store one tree per entity, that is a read crossing into another entity's data with no error to tell you. Fixed on all six provider paths, Free and Pro, with a regression test asserting isolation on every fixture.

SumRedbAsync / AverageRedbAsync no longer throw on an empty selection. A SUM/AVG over no matching rows is NULL in SQL, and the result was read through JsonElement.GetDecimal, which throws on null. Both now return 0m, matching Enumerable.Sum semantics and the NULL guard that Min/Max already had. The path only became reachable after 3.5.0 made base-field aggregations honour the filter.

The SQLite native extension was rebuilt for every RID. Part of the tree fix lives in redb_pvt.c, so a package carrying the old binaries would ship the fix on the managed side and leave the Free tier leaking across trees. win-x64, linux-x64 and linux-arm64 are rebuilt from current source and verified byte-different from 3.5.0. macOS still ships no prebuilt extension and must be compiled from source.

Upgrading

Drop-in for the managed packages. If you run the Free SQLite tier, take the new native binaries with it, otherwise you keep the tree defect. Linux and macOS builds compiled from source need recompiling per platform.

Why a minor and not a patch

redb.Route adds public API in this release, and new surface cannot ship as a patch. The core packages carry only fixes, but the ecosystem moves on one number. This also re-unifies the line after 3.5.1, where Route, Tsak and Identity moved while the core stayed at 3.5.0. All four are on 3.6.0 again.

Links

• Release v3.6.0
• Full changelog

Questions, upgrade trouble, or something that behaves differently than you expected? Reply here or open a thread in Q&A. Anyone can post, no permissions needed.