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

[Noriko Hosoi <nhosoi@xxxxxxxxxx>]

https://fedorahosted.org/389/ticket/274

https://fedorahosted.org/389/attachment/ticket/274/0001-Trac-Ticket-274-Reindexing-entryrdn-fails-if.patch

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