[389-devel] Please review: [389 Project] #274: Reindexing entryrdn fails if ancestors are also tombstoned

Subject: [389-devel] Please review: [389 Project] #274: Reindexing entryrdn fails if ancestors are also tombstoned
From: Noriko Hosoi <nhosoi@xxxxxxxxxx>
Date: Tue, 31 Jan 2012 16:14:06 -0800
Delivered-to: 389-devel@xxxxxxxxxxxxxxxxxxxxxxx
In-reply-to: <036.a1d3a7bffd4f5030ab65210ee7a324e1@fedorahosted.org>
References: <036.a1d3a7bffd4f5030ab65210ee7a324e1@fedorahosted.org>
Reply-to: "389 Directory server developer discussion." <389-devel@xxxxxxxxxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16

Bug description: Inserting/traversing entryrdn fails if a parent
entry is tombstoned and the rdn in the entryrdn index includes
nsuniqueid.

In DIT cn=A,ou=B,o=C, cn=A and ou=B are removed and turned to
tombstone entries. Both of the 2 representations need to be
supported in the entryrdn.

nsuniqueid=...,cn=A,ou=B,o=C and
nsuniqueid=...,cn=A,nsuniqueid=...,ou=B,o=C

Fix description: Support for the second case is added by this patch.
Also, in index_add_mods, code for checking NULL mods is added.

--
389-devel mailing list
389-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-devel