openldap-bugs

openldap-bugs@openldap.org

1 participants
20964 discussions

Re: (ITS#8913) Add meson build system to lmdb
by nacho.resa＠gmail.com 05 Sep '18

05 Sep '18

--0000000000007aaf1005752283b9 Content-Type: text/plain; charset="UTF-8" FWIW any chance to reconsider having both build systems? with meson it is easy to build on windows. Plus I'd like you to see at these numbers: time make: real 0m5.629s user 0m5.197s sys 0m0.399s time meson build real 0m0.452s user 0m0.335s sys 0m0.131s time ninja -C build real 0m0.992s user 0m1.812s sys 0m0.362s You can see that configuring and building with meson is faster than just using make On Wed, Sep 5, 2018 at 6:31 PM Ignacio Casal Quinteiro <nacho.resa(a)gmail.com> wrote: > yeah... knowing my previous tries with lmdb I did not have much hope... > > On Wed, Sep 5, 2018 at 6:21 PM Howard Chu <hyc(a)symas.com> wrote: > >> nacho.resa(a)gmail.com wrote: >> > Full_Name: Ignacio Casal Quinteiro >> > Version: >> > OS: >> > URL: ftp://ftp.openldap.org/incoming/ >> > Submission from: (NULL) (54.239.6.177) >> > >> > >> > Meson is the new thing out there, >> >> No. >> >> >> -- >> -- Howard Chu >> CTO, Symas Corp. http://www.symas.com >> Director, Highland Sun http://highlandsun.com/hyc/ >> Chief Architect, OpenLDAP http://www.openldap.org/project/ >> > > > -- > Ignacio Casal Quinteiro > -- Ignacio Casal Quinteiro --0000000000007aaf1005752283b9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div di= r=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>FWIW any chance to reconsi= der having both build systems?</div><div>with meson it is easy to build on = windows. Plus I'd like you</div><div>to see at these numbers:</div><div= ><br></div><div>time make:</div><div>real=C2=A0=C2=A0=C2=A0 0m5.629s<br>use= r=C2=A0=C2=A0=C2=A0 0m5.197s<br>sys=C2=A0=C2=A0=C2=A0 0m0.399s<br></div><di= v><br></div><div>time meson build</div><div>real=C2=A0=C2=A0=C2=A0 0m0.452s= <br>user=C2=A0=C2=A0=C2=A0 0m0.335s<br>sys=C2=A0=C2=A0=C2=A0 0m0.131s<br></= div><div><br></div><div>time ninja -C build</div><div>real=C2=A0=C2=A0=C2= =A0 0m0.992s<br>user=C2=A0=C2=A0=C2=A0 0m1.812s<br>sys=C2=A0=C2=A0=C2=A0 0m= 0.362s<br></div><div><br></div><div>You can see that configuring and buildi= ng with meson is faster than just using make<br></div></div></div></div></d= iv></div></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed= , Sep 5, 2018 at 6:31 PM Ignacio Casal Quinteiro <<a href=3D"mailto:nach= o.resa(a)gmail.com">nacho.resa(a)gmail.com</a>> wrote:<br></div><blockquote = class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid= ;padding-left:1ex"><div dir=3D"ltr">yeah... knowing my previous tries with = lmdb I did not have much hope...<br></div><br><div class=3D"gmail_quote"><d= iv dir=3D"ltr">On Wed, Sep 5, 2018 at 6:21 PM Howard Chu <<a href=3D"mai= lto:hyc@symas.com" target=3D"_blank">hyc(a)symas.com</a>> wrote:<br></div>= <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"><a href=3D"mailto:nacho.resa@gmail.com" targ= et=3D"_blank">nacho.resa(a)gmail.com</a> wrote:<br> > Full_Name: Ignacio Casal Quinteiro<br> > Version: <br> > OS: <br> > URL: <a href=3D"ftp://ftp.openldap.org/incoming/" rel=3D"noreferrer" t= arget=3D"_blank">ftp://ftp.openldap.org/incoming/</a><br> > Submission from: (NULL) (54.239.6.177)<br> > <br> > <br> > Meson is the new thing out there,<br> <br> No.<br> <br> <br> -- <br> =C2=A0 -- Howard Chu<br> =C2=A0 CTO, Symas Corp.=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"= http://www.symas.com" rel=3D"noreferrer" target=3D"_blank">http://www.symas= .com</a><br> =C2=A0 Director, Highland Sun=C2=A0 =C2=A0 =C2=A0<a href=3D"http://highland= sun.com/hyc/" rel=3D"noreferrer" target=3D"_blank">http://highlandsun.com/h= yc/</a><br> =C2=A0 Chief Architect, OpenLDAP=C2=A0 <a href=3D"http://www.openldap.org/p= roject/" rel=3D"noreferrer" target=3D"_blank">http://www.openldap.org/proje= ct/</a><br> </blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr" class=3D"m= _-8944057145512108354gmail_signature" data-smartmail=3D"gmail_signature">Ig= nacio Casal Quinteiro</div> </blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr" class=3D"g= mail_signature" data-smartmail=3D"gmail_signature">Ignacio Casal Quinteiro<= /div> --0000000000007aaf1005752283b9--

1 0

Re: (ITS#8913) Add meson build system to lmdb
by nacho.resa＠gmail.com 05 Sep '18

05 Sep '18

--000000000000a46a9a05752250a1 Content-Type: text/plain; charset="UTF-8" yeah... knowing my previous tries with lmdb I did not have much hope... On Wed, Sep 5, 2018 at 6:21 PM Howard Chu <hyc(a)symas.com> wrote: > nacho.resa(a)gmail.com wrote: > > Full_Name: Ignacio Casal Quinteiro > > Version: > > OS: > > URL: ftp://ftp.openldap.org/incoming/ > > Submission from: (NULL) (54.239.6.177) > > > > > > Meson is the new thing out there, > > No. > > > -- > -- Howard Chu > CTO, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/project/ > -- Ignacio Casal Quinteiro --000000000000a46a9a05752250a1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">yeah... knowing my previous tries with lmdb I did not have= much hope...<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On W= ed, Sep 5, 2018 at 6:21 PM Howard Chu <<a href=3D"mailto:hyc@symas.com">= hyc(a)symas.com</a>> wrote:<br></div><blockquote class=3D"gmail_quote" sty= le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><a hre= f=3D"mailto:nacho.resa@gmail.com" target=3D"_blank">nacho.resa(a)gmail.com</a= > wrote:<br> > Full_Name: Ignacio Casal Quinteiro<br> > Version: <br> > OS: <br> > URL: <a href=3D"ftp://ftp.openldap.org/incoming/" rel=3D"noreferrer" t= arget=3D"_blank">ftp://ftp.openldap.org/incoming/</a><br> > Submission from: (NULL) (54.239.6.177)<br> > <br> > <br> > Meson is the new thing out there,<br> <br> No.<br> <br> <br> -- <br> =C2=A0 -- Howard Chu<br> =C2=A0 CTO, Symas Corp.=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"= http://www.symas.com" rel=3D"noreferrer" target=3D"_blank">http://www.symas= .com</a><br> =C2=A0 Director, Highland Sun=C2=A0 =C2=A0 =C2=A0<a href=3D"http://highland= sun.com/hyc/" rel=3D"noreferrer" target=3D"_blank">http://highlandsun.com/h= yc/</a><br> =C2=A0 Chief Architect, OpenLDAP=C2=A0 <a href=3D"http://www.openldap.org/p= roject/" rel=3D"noreferrer" target=3D"_blank">http://www.openldap.org/proje= ct/</a><br> </blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr" class=3D"g= mail_signature" data-smartmail=3D"gmail_signature">Ignacio Casal Quinteiro<= /div> --000000000000a46a9a05752250a1--

1 0

Re: (ITS#8913) Add meson build system to lmdb
by hyc＠symas.com 05 Sep '18

05 Sep '18

nacho.resa(a)gmail.com wrote: > Full_Name: Ignacio Casal Quinteiro > Version: > OS: > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (54.239.6.177) > > > Meson is the new thing out there, No. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#8913) Add meson build system to lmdb
by nacho.resa＠gmail.com 05 Sep '18

05 Sep '18

Full_Name: Ignacio Casal Quinteiro Version: OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (54.239.6.177) Meson is the new thing out there, maybe projects are already using it and allows embedding in other projects apart from being fast, efficient and easier to maintain than a Makefile. On the following patch you can find a working meson build system which builds lmdb: https://github.com/wingtk/lmdb/commit/24b1b1ce2055b6a612603700bdcfc7ba3859f…

1 0

Re: (ITS#8910) Open Ldap back sql installation Query
by Howard Chu 05 Sep '18

05 Sep '18

The OpenLDAP-ITS address is for reporting bugs in OpenLDAP software. Nothing in your report is indicative of a bug in OpenLDAP. If you have questions about use of OpenLDAP Software which are not answered in the documentation, FAQ, and archives, use the OpenLDAP-technical list (subscription required; instructions here <http://www.openldap.org/lists/mm/listinfo/openldap-technical>). This issue report will be closed. p.

1 0

Re: (ITS#8912) incorrect rootDSE (namingContexts)
by hyc＠symas.com 05 Sep '18

05 Sep '18

jochen(a)keutel.de wrote: > Full_Name: Jochen Keutel > Version: 2.4.46 > OS: Debian 9 > URL: > Submission from: (NULL) (80.146.191.218) > > > With certain configurations it happens that the attribute namingContexts of the > rootDSE contains the same value twice (which is not correct). It seems to be > related to the fact that the naming context of a hidden backend is not ignored > (servers/slapd/root_dse.c). Thanks for the report. Fixed now in git master. > > To reproduce it: I started to configure replication: szenario syncrepl proxy > (push based replication, see 18.3.5 in OpenLDAP Admin Guide - "primary directory > also contains back-ldap databases"). Configuring the LDAP backend leads > unfortunately to a root DSE showing the same name context twice: > > namingContexts: dc=keutel,dc=de > namingContexts: dc=keutel,dc=de > > Is this a known problem? Esp. this stops PHPLDAPAdmin from working: It prints a > lot of PHP arrays in this case. > > I've set "hidden on" for this backend but the problem remains. > > My configuration: > > 1. slapd.conf on server1 (master): > > database mdb > suffix "dc=keutel,dc=de" > ... > > database ldap > hidden on > suffix "dc=keutel,dc=de" > rootdn "cn=admin,dc=keutel,dc=de" > uri ldaps://server2/ > > lastmod on > restrict all > > acl-bind bindmethod=simple > binddn="cn=replication,dc=keutel,dc=de" > credentials=secret > > syncrepl rid=001 > provider=ldaps://server1/ > binddn="cn=replication,dc=keutel,dc=de" > bindmethod=simple > credentials=secret > searchbase="dc=keutel,dc=de" > type=refreshAndPersist > retry="5 5 300 5" > > 2. converting this to dynamic config using slaptest gives the following entry: > > > dn: olcDatabase={2}ldap > objectClass: olcDatabaseConfig > objectClass: olcLDAPConfig > olcDatabase: {2}ldap > olcHidden: TRUE > olcSuffix: dc=keutel,dc=de > ... > > 3. starting slapd with this dynamic configuration > > 4. reading rootDSE: attribute namingContexts occurs twice with the same value. > > > > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#8912) incorrect rootDSE (namingContexts)
by jochen＠keutel.de 04 Sep '18

04 Sep '18

Full_Name: Jochen Keutel Version: 2.4.46 OS: Debian 9 URL: Submission from: (NULL) (80.146.191.218) With certain configurations it happens that the attribute namingContexts of the rootDSE contains the same value twice (which is not correct). It seems to be related to the fact that the naming context of a hidden backend is not ignored (servers/slapd/root_dse.c). To reproduce it: I started to configure replication: szenario syncrepl proxy (push based replication, see 18.3.5 in OpenLDAP Admin Guide - "primary directory also contains back-ldap databases"). Configuring the LDAP backend leads unfortunately to a root DSE showing the same name context twice: namingContexts: dc=keutel,dc=de namingContexts: dc=keutel,dc=de Is this a known problem? Esp. this stops PHPLDAPAdmin from working: It prints a lot of PHP arrays in this case. I've set "hidden on" for this backend but the problem remains. My configuration: 1. slapd.conf on server1 (master): database mdb suffix "dc=keutel,dc=de" ... database ldap hidden on suffix "dc=keutel,dc=de" rootdn "cn=admin,dc=keutel,dc=de" uri ldaps://server2/ lastmod on restrict all acl-bind bindmethod=simple binddn="cn=replication,dc=keutel,dc=de" credentials=secret syncrepl rid=001 provider=ldaps://server1/ binddn="cn=replication,dc=keutel,dc=de" bindmethod=simple credentials=secret searchbase="dc=keutel,dc=de" type=refreshAndPersist retry="5 5 300 5" 2. converting this to dynamic config using slaptest gives the following entry: dn: olcDatabase={2}ldap objectClass: olcDatabaseConfig objectClass: olcLDAPConfig olcDatabase: {2}ldap olcHidden: TRUE olcSuffix: dc=keutel,dc=de ... 3. starting slapd with this dynamic configuration 4. reading rootDSE: attribute namingContexts occurs twice with the same value.

1 0

Re: (ITS#8911) Open LDAP 2.4 MMR with delta-sync replication
by hyc＠symas.com 30 Aug '18

30 Aug '18

The ITS is for bug reports not help requests. Use the openldap-technical mailing list. sakshi.mittal(a)india.nec.com wrote: > Full_Name: Sakshi Mittal > Version: 2.4.44 > OS: Centos7 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (14.140.114.207) > > > We are trying to setup MMR with delta sync replication in OpenLDAP 2.4.44. > > We have two provider servers and 2 consumer servers. We have setup delta sync > replication between the provider and consumer servers. > Now we want to configure MMR between the two provider servers. > But it does not seem to work together with delta sync. > > I have tried setting up MMR separately and it works also delta sync replication > also works separately. > > Can you please help in configuring the two together also please let me know if > this is even possible. As on some sites it is written that OpenLDAP 2.4 does not > support MMR together with delta-sync replication. > > Please confirm. > > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#8911) Open LDAP 2.4 MMR with delta-sync replication
by sakshi.mittal＠india.nec.com 29 Aug '18

29 Aug '18

Full_Name: Sakshi Mittal Version: 2.4.44 OS: Centos7 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (14.140.114.207) We are trying to setup MMR with delta sync replication in OpenLDAP 2.4.44. We have two provider servers and 2 consumer servers. We have setup delta sync replication between the provider and consumer servers. Now we want to configure MMR between the two provider servers. But it does not seem to work together with delta sync. I have tried setting up MMR separately and it works also delta sync replication also works separately. Can you please help in configuring the two together also please let me know if this is even possible. As on some sites it is written that OpenLDAP 2.4 does not support MMR together with delta-sync replication. Please confirm.

1 0

Re: (ITS#8908) LMDB Documentation for MDB_XXX_MULTIPLE
by karl＠waclawek.net 29 Aug '18

29 Aug '18

--000000000000a517d40574956804 Content-Type: text/plain; charset="UTF-8" Thanks! On Wed, Aug 29, 2018, 12:05 Howard Chu, <hyc(a)symas.com> wrote: > karl(a)waclawek.net wrote: > > --00000000000018b43a057492d87f > > Content-Type: text/plain; charset="UTF-8" > > > > As far as point 2 is concerned I was basing it on this piece of code, > where > > it looks like MDB_GET_MULTIPLE just checks some flags and then goes to > the > > fetchm label where the code does nothing but retrieve data: > > You're not reading the code correctly. See below. > > > > case MDB_GET_MULTIPLE: > > if (data == NULL || !(mc->mc_flags & C_INITIALIZED)) { > > rc = EINVAL; > > break; > > } > > if (!(mc->mc_db->md_flags & MDB_DUPFIXED)) { > > rc = MDB_INCOMPATIBLE; > > break; > > } > > rc = MDB_SUCCESS; > > if (!(mc->mc_xcursor->mx_cursor.mc_flags & C_INITIALIZED) || > > (mc->mc_xcursor->mx_cursor.mc_flags & C_EOF)) > > break; > > goto fetchm; > > case MDB_NEXT_MULTIPLE: > > if (data == NULL) { > > rc = EINVAL; > > break; > > } > > if (!(mc->mc_db->md_flags & MDB_DUPFIXED)) { > > rc = MDB_INCOMPATIBLE; > > break; > > } > > rc = mdb_cursor_next(mc, key, data, MDB_NEXT_DUP); > > if (rc == MDB_SUCCESS) { > > if (mc->mc_xcursor->mx_cursor.mc_flags & C_INITIALIZED) { > > MDB_cursor *mx; > > fetchm: > > mx = &mc->mc_xcursor->mx_cursor; > > data->mv_size = NUMKEYS(mx->mc_pg[mx->mc_top]) * > > mx->mc_db->md_pad; > > data->mv_data = METADATA(mx->mc_pg[mx->mc_top]); > > mx->mc_ki[mx->mc_top] = NUMKEYS(mx->mc_pg[mx->mc_top])-1; > > ^^^ this line advances the cursor. > > > } else { > > rc = MDB_NOTFOUND; > > } > > } > > break; > > > > > > On Tue, Aug 28, 2018 at 8:26 PM Howard Chu <openldap-its(a)openldap.org> > > wrote: > > > >>> Full_Name: Karl Waclawek > >>> Version: LMDB 0.9.22 > >>> OS: Windows 10 > >>> URL: ftp://ftp.openldap.org/incoming/ > >>> Submission from: (NULL) (2607:fea8:7a80:814:3ca9:e8f6:801c:d6f8) > >>> > >>> > >>> The documentation in lmdb.h for MDB_GET_MULTIPLE, MDB_NEXT_MULTIPLE and > >>> MDB_PREV_MULTIPLE seems to have two issues: > >>> > >>> 1) The documentation indicates that both, the key and data, are > >> returned, but > >> in > >>> reality only the data is returned. > >> > >> Looks like you're right. Since these are DUPs the key would be the same > >> every time so there's no need to return it on each call. > >> Doc fixed in git mdb.master. > >> > >>> 2) The documentation states that MDB_GET_MULTIPLE moves the cursor. > This > >> does > >>> not seem to be true. > >> > >> The doc is correct here. The cursor is advanced far enough that a > >> MDB_NEXT_MULTIPLE will return the following data, as opposed to just > >> returning the same data again. > >> > > > > > > -- > -- Howard Chu > CTO, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/project/ > --000000000000a517d40574956804 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">Thanks!</div><br><div class=3D"gmail_quote"><div dir=3D"l= tr">On Wed, Aug 29, 2018, 12:05 Howard Chu, <<a href=3D"mailto:hyc@symas= .com">hyc(a)symas.com</a>> wrote:<br></div><blockquote class=3D"gmail_quot= e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">= <a href=3D"mailto:karl@waclawek.net" target=3D"_blank" rel=3D"noreferrer">k= arl(a)waclawek.net</a> wrote:<br> > --00000000000018b43a057492d87f<br> > Content-Type: text/plain; charset=3D"UTF-8"<br> > <br> > As far as point 2 is concerned I was basing it on this piece of code, = where<br> > it looks like MDB_GET_MULTIPLE just checks some flags and then goes to= the<br> > fetchm label where the code does nothing but retrieve data:<br> <br> You're not reading the code correctly. See below.<br> > <br> > case MDB_GET_MULTIPLE:<br> > if (data =3D=3D NULL || !(mc->mc_flags & C_INITIALIZED)) {<br> > rc =3D EINVAL;<br> > break;<br> > }<br> > if (!(mc->mc_db->md_flags & MDB_DUPFIXED)) {<br> > rc =3D MDB_INCOMPATIBLE;<br> > break;<br> > }<br> > rc =3D MDB_SUCCESS;<br> > if (!(mc->mc_xcursor->mx_cursor.mc_flags & C_INITIALIZED) ||= <br> > (mc->mc_xcursor->mx_cursor.mc_flags & C_EOF))<br> > break;<br> > goto fetchm;<br> > case MDB_NEXT_MULTIPLE:<br> > if (data =3D=3D NULL) {<br> > rc =3D EINVAL;<br> > break;<br> > }<br> > if (!(mc->mc_db->md_flags & MDB_DUPFIXED)) {<br> > rc =3D MDB_INCOMPATIBLE;<br> > break;<br> > }<br> > rc =3D mdb_cursor_next(mc, key, data, MDB_NEXT_DUP);<br> > if (rc =3D=3D MDB_SUCCESS) {<br> > if (mc->mc_xcursor->mx_cursor.mc_flags & C_INITIALIZED) {<br= > > MDB_cursor *mx;<br> > fetchm:<br> > mx =3D &mc->mc_xcursor->mx_cursor;<br> > data->mv_size =3D NUMKEYS(mx->mc_pg[mx->mc_top]) *<br> > mx->mc_db->md_pad;<br> > data->mv_data =3D METADATA(mx->mc_pg[mx->mc_top]);<br> > mx->mc_ki[mx->mc_top] =3D NUMKEYS(mx->mc_pg[mx->mc_top])-1= ;<br> <br> ^^^ this line advances the cursor.<br> <br> > } else {<br> > rc =3D MDB_NOTFOUND;<br> > }<br> > }<br> > break;<br> > <br> > <br> > On Tue, Aug 28, 2018 at 8:26 PM Howard Chu <<a href=3D"mailto:openl= dap-its(a)openldap.org" target=3D"_blank" rel=3D"noreferrer">openldap-its@ope= nldap.org</a>><br> > wrote:<br> > <br> >>> Full_Name: Karl Waclawek<br> >>> Version: LMDB 0.9.22<br> >>> OS: Windows 10<br> >>> URL: <a href=3D"ftp://ftp.openldap.org/incoming/" rel=3D"noref= errer noreferrer" target=3D"_blank">ftp://ftp.openldap.org/incoming/</a><br= > >>> Submission from: (NULL) (2607:fea8:7a80:814:3ca9:e8f6:801c:d6f= 8)<br> >>><br> >>><br> >>> The documentation in lmdb.h for MDB_GET_MULTIPLE, MDB_NEXT_MUL= TIPLE and<br> >>> MDB_PREV_MULTIPLE seems to have two issues:<br> >>><br> >>> 1) The documentation indicates that both, the key and data, ar= e<br> >> returned, but<br> >> in<br> >>> reality only the data is returned.<br> >><br> >> Looks like you're right. Since these are DUPs the key would be= the same<br> >> every time so there's no need to return it on each call.<br> >> Doc fixed in git mdb.master.<br> >><br> >>> 2) The documentation states that MDB_GET_MULTIPLE moves the cu= rsor. This<br> >> does<br> >>> not seem to be true.<br> >><br> >> The doc is correct here. The cursor is advanced far enough that a<= br> >> MDB_NEXT_MULTIPLE will return the following data, as opposed to ju= st<br> >> returning the same data again.<br> >><br> > <br> <br> <br> <br> -- <br> =C2=A0 =C2=A0-- Howard Chu<br> =C2=A0 =C2=A0CTO, Symas Corp.=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a hr= ef=3D"http://www.symas.com" rel=3D"noreferrer noreferrer" target=3D"_blank"= >http://www.symas.com</a><br> =C2=A0 =C2=A0Director, Highland Sun=C2=A0 =C2=A0 =C2=A0<a href=3D"http://hi= ghlandsun.com/hyc/" rel=3D"noreferrer noreferrer" target=3D"_blank">http://= highlandsun.com/hyc/</a><br> =C2=A0 =C2=A0Chief Architect, OpenLDAP=C2=A0 <a href=3D"http://www.openldap= .org/project/" rel=3D"noreferrer noreferrer" target=3D"_blank">http://www.o= penldap.org/project/</a><br> </blockquote></div> --000000000000a517d40574956804--

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs