Full_Name: Pierangelo Masarati Version: HEAD / RE22 OS: Linux (irrelevant?) URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (131.175.154.56) The deletion of the entry corresponding to the suffix of a database fails with "Operation not allowed on nonleaf (66)" when bdb/hdb is used, I suspect because the "cn=syncrepl,<suffix>" entry is defined, although hidden. It works fine, for instance, when back-ldbm is used. p.
ando@sys-net.it wrote: >Full_Name: Pierangelo Masarati >Version: HEAD / RE22 >OS: Linux (irrelevant?) >URL: ftp://ftp.openldap.org/incoming/ >Submission from: (NULL) (131.175.154.56) > > >The deletion of the entry corresponding to the suffix of a database fails with >"Operation not allowed on nonleaf (66)" when bdb/hdb is used, I suspect because >the "cn=syncrepl,<suffix>" entry is defined, although hidden. > >It works fine, for instance, when back-ldbm is used. > Interesting. This suggests to me that the CSN context should just be an operational attribute attached to the root/suffix entry of the database. That would also save a lot of nonsense with creating the context entry and other such stuff. I'll try this approach in my overlay... -- -- Howard Chu Chief Architect, Symas Corp. Director, Highland Sun http://www.symas.com http://highlandsun.com/hyc Symas: Premier OpenSource Development and Support
> Interesting. This suggests to me that the CSN context should just be an > operational attribute attached to the root/suffix entry of the database. > That would also save a lot of nonsense with creating the context entry > and other such stuff. I'll try this approach in my overlay... That's not a big deal for me, I was just playing with "ldapdelete -r". However, I think this part should really need to be reworked, syncprov or not. p. -- Pierangelo Masarati mailto:pierangelo.masarati@sys-net.it SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497
Pierangelo Masarati wrote: >>Interesting. This suggests to me that the CSN context should just be an >>operational attribute attached to the root/suffix entry of the database. >>That would also save a lot of nonsense with creating the context entry >>and other such stuff. I'll try this approach in my overlay... >> >> > >That's not a big deal for me, I was just playing with "ldapdelete -r". >However, I think this part should really need to be reworked, syncprov or >not. > Ah right. The ldapdelete code needs to use a search that includes subentries, i.e., add a subentries control with visibility True. -- -- Howard Chu Chief Architect, Symas Corp. Director, Highland Sun http://www.symas.com http://highlandsun.com/hyc Symas: Premier OpenSource Development and Support
changed notes changed state Open to Test
changed notes moved from Incoming to Software Bugs
> Ah right. The ldapdelete code needs to use a search that includes > subentries, i.e., add a subentries control with visibility True. Works for me. Thanks, p. -- Pierangelo Masarati mailto:pierangelo.masarati@sys-net.it SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497
changed state Test to Release
Note that subentries control of TRUE means to ONLY return subentries. You seem to want a control which requests all entries and subentries be returned. That beast doesn't exist.
Kurt Zeilenga wrote: >Note that subentries control of TRUE means to ONLY return subentries. >You seem to want a control which requests all entries and subentries >be returned. That beast doesn't exist. > > Understood. I see that Jong committed the appropriate client fix. -- -- Howard Chu Chief Architect, Symas Corp. Director, Highland Sun http://www.symas.com http://highlandsun.com/hyc Symas: Premier OpenSource Development and Support
changed state Release to Closed
moved from Software Bugs to Archive.Software Bugs
ldapdelete & back-bdb fixed in HEAD