https://bugs.openldap.org/show_bug.cgi?id=9476
Howard Chu <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Howard Chu <[email protected]> --- (In reply to jaqenn from comment #0) > The documentation for MDB_GET_BOTH_RANGE is incorrect. > > This operation is documented as 'position at key, nearest data'. It appears > to me that it should instead say 'position at key, first data greater than > or equal to specified data'. > > If I call mdb_cursor_get with a valid key and a data smaller than all > existing values, then lmdb returns MDB_SUCCESS and the cursor is positioned > at the first value. > > If I call mdb_cursor_get with a valid key and a data larger than all > existing values, then lmdb returns MDB_NOTFOUND and the cursor is not > repositioned. > > The documentation 'nearest data' makes me expect that if I call > mdb_cursor_get with a valid key and a data larger than all existing values, > then lmdb would return MDB_SUCCESS and the cursor is positioned at the last > value. RANGE in this case means the same as for MDB_SET_RANGE. The documentation "nearest data" was written for brevity on the assumption that readers would understand that concept was the same as above. -- You are receiving this mail because: You are on the CC list for the issue.
