Re^2: fast+generic interface for range-based indexed retrieval

Aha, with DB_SET_RANGE.

Otherwise, I was wondering if storing a bitmap of the keys used would be useful. Probably not.

Comment on Re^2: fast+generic interface for range-based indexed retrieval

Replies are listed 'Best First'.
Re^3: fast+generic interface for range-based indexed retrieval by perrin (Chancellor) on Dec 12, 2008 at 08:18 UTC
No, you don't need DB_SET_RANGE. You get the cursor on the key you want with DB_GET and then keep calling DB_NEXT until you're done.	[reply]