[prev in list] [next in list] [prev in thread] [next in thread]
List: openldap-technical
Subject: Re: LMDB cursor position
From: M Gurschi <max.gurschi () gmail ! com>
Date: 2024-02-01 20:21:21
Message-ID: D4E03CED-7979-4B3C-BDCF-062FE789A632 () gmail ! com
[Download RAW message or body]
Understood, thank you!
Kind Regards,
Maxim Gurschi
On 1 Feb 2024, at 17:53, Howard Chu <hyc@symas.com> wrote:
M Gurschi wrote:
> Hello team,
>
> Can you please let me know, when using *mdb_cursor_get* with *MDB_SET* operation, \
> in case the key is not present in the db, where is the cursor left pointing?
> My scenario is that i want to retrieve two adjacent keys.
>
> 1. first *mdb_cursor_get* with *MDB_SET*
> 2. after that, *mdb_cursor_get* with *MDB_NEXT*
>
> I'm wondering what can i expect the cursor to point at in case the key is not found \
> in step 1.
You cannot expect anything in particular.
Use MDB_SET_RANGE instead.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic