[Date Prev][Date Next]
Re: (ITS#7570) fix MDB_GET_MULTIPLE and MDB_NEXT_MULTIPLE behaviour
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#7570) fix MDB_GET_MULTIPLE and MDB_NEXT_MULTIPLE behaviour
- From: firstname.lastname@example.org
- Date: Sun, 14 Apr 2013 23:46:17 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
> Full_Name: Claude Brisson
> Version: HEAD
> OS: linux 64
> URL: ftp://ftp.openldap.org/incoming/0001-fix-MDB_GET_MULTIPLE-and-MDB_NEXT_MULTIPLE.patch
> Submission from: (NULL) (18.104.22.168)
> In a db with MDB_DUPSORT flag, when there is only one DUP data for a key,
> F_DUPDATA is not set for this key, and there is no sub-cursor.
> In this case, the current behaviour of MDB_GET_MULTIPLE and MDB_NEXT_MULTIPLE is
> broken because they make the assumption that there is always a sub-cursor for
> DUP data, which is only true for keys with more than one DUP data.
> This patch address this specific issue.
Something's wrong with this patch, it breaks MDB_GET_MULTIPLE/NEXT_MULTIPLE
usage in slapd. Need to investigate further.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/