[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Question about LibLmdb MDB_GET_BOTH_RANGE and MDB_SET_RANGE
- To: Tim Uckun <timuckun@gmail.com>
- Subject: Re: Question about LibLmdb MDB_GET_BOTH_RANGE and MDB_SET_RANGE
- From: Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no>
- Date: Fri, 2 Dec 2016 13:48:58 +0100
- Cc: openldap-technical@openldap.org
- In-reply-to: <CAGuHJrPqA=ivwW15ry5a72FE5soT+n1ocZx2oJYPcu5UWcNyiw@mail.gmail.com>
- References: <CAGuHJrPqA=ivwW15ry5a72FE5soT+n1ocZx2oJYPcu5UWcNyiw@mail.gmail.com>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
On 02. des. 2016 12:18, Tim Uckun wrote:
(...)
cur.find_ge(".", "1.2") #this uses GET_BOTH_RANGE
(...)
but the second call results in a MDB_NOTFOUND
GET_BOTH_RANGE is (exact key, inexact data).
There is no (inexact key, inexact data) search operation.
--
Hallvard