1) As reported by baburaje12, regardless of the nsslapd-subtree-
rename-switch, "entrydn" was not stored in the id2entry db. The
attribute value had to be stored in the db file if the switch
was off. Attribute values to avoid storing in the db file are
maintained in an array protected_attrs_all statically. "Entrydn"
should be dynamic depending on the switch.
2) When the switch is off, import was skipping to generate the
parentid index, which leads to skipping to create the entrydn,
1) Instead of keeping "entrydn" in the protected_attrs_all statically,
this patch introduces an api set_attr_to_protected_list to add or
remove "entrydn" based upon the value of nsslapd-subtree-rename-
2) The condition to create a parentid index is fixed to always
create it if the nsslapd-subtree-rename-switch is off.
1. When the key format of entryrdn was updated (eliminated ':'
from the key), the dbscan was not updated.
2. If a key is passed with -k option and if the key has multiple
values, only the first one was printed.
1. The key format is adjusted to the entryrdn code.
2. Multi-valued key is supported.
dbscan -f entryrdn.db
Scan entryrdn based on the order of the key (oid - 1,2,...,
Coid - C1,C2,..., Poid - P1,P2,...).
dbscan -f engryrdn.db -k key
where the key could be "suffix" or key (oid, Coid, Poid)
The scan starts from the item of the key and traverses its