Summary

The release corrects range(), extract_from_if(), and retain_in() when a range starts after it ends and the keys are separated across internal B-tree pages. Previously, those cases could be treated as an unbounded start range.

Why it matters

Correct range semantics are foundational for embedded databases because silent misinterpretation can produce incorrect reads or mutations in applications built on the storage layer.

Sources