William Casarin 8e361a9586 nostrdb/search: fix subtle bug with some newest-first text search ...

Due to the way the range queries work for newest-first searches, we can
have a situation where the MDB_SET_RANGE gets placed on either the
correct place or just after the correct place. To position the cursor
correctly, we jump back one if the search result prefix doesn't match.

Signed-off-by: William Casarin <jb55@jb55.com>

2023-12-02 13:44:03 -08:00

110 KiB

Raw Blame History

View Raw