Issue 8393 - LMDB - MDB_GET_BOTH broken on non-dup value
Summary: LMDB - MDB_GET_BOTH broken on non-dup value
Status: VERIFIED FIXED
Alias: None
Product: LMDB
Classification: Unclassified
Component: liblmdb (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-28 00:35 UTC by Howard Chu
Modified: 2020-03-12 15:55 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Howard Chu 2016-03-28 00:35:47 UTC
Full_Name: Howard Chu
Version: 0.9.18
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (78.155.228.110)
Submitted by: hyc


Using mdb_cursor_get(MDB_GET_BOTH) doesn't return the data item if the record is
not a dup (i.e., there's only a single value under the key) even though it
matches. 

This doesn't affect slapd because (1) when we use this command, the key always
has more than 1 value and (2) when we use it, the data item we passed in is
exactly the same as what we would get returned, on a match.

This affects other apps where both (1) and (2) are not true, e.g. a compare
function is used that only compares a subset of the data, in order to retrieve
the full record.
Comment 1 Howard Chu 2016-03-28 00:37:07 UTC
changed notes
changed state Open to Test
moved from Incoming to Software Bugs
Comment 2 OpenLDAP project 2018-02-09 18:57:46 UTC
fixed in mdb.master
Fixed in 0.9.19
Comment 3 Quanah Gibson-Mount 2018-02-09 18:57:46 UTC
changed notes
changed state Test to Closed