[ http://issues.apache.org/jira/browse/DIREVE-173?page=comments#action_12318125 ]
Stefan Zoerner commented on DIREVE-173: --------------------------------------- I think it depends on the modify DN operations parameters whether the old RDN value is kept or not. Example: --8<-- # create an entry for a person # dn: cn=Myra Ellen Amos,ou=system changetype: add objectclass: top objectclass: person cn: Myra Ellen Amos sn: Amos description: an American singer-songwriter # Change RDN # old RDN value of cn should continue to be in place # dn: cn=Myra Ellen Amos,ou=system changetype: modrdn newrdn: cn=Tori Amos deleteoldrdn: 1 -->8-- The deleteoldrdn may be 0 or 1. 0 keeps the old RDN value, 1 deletes it. When I apply the above LDIF to a 0.9.1 ApacheDS, $ ldapmodify -p 10389 -D uid=admin,ou=system -w ***** -f modRdn.ldif adding new entry cn=Myra Ellen Amos,ou=system moving cn=Myra Ellen Amos,ou=system to cn=Tori Amos And the entry of Tori looks like: dn: cn=Tori Amos,ou=system sn: Amos objectclass: person objectclass: top cn: Tori Amos description: an American singer-songwriter The test with deleteoldrdn=0 works as well. > On modifyRdn server now adds additional Rdn attribute > ----------------------------------------------------- > > Key: DIREVE-173 > URL: http://issues.apache.org/jira/browse/DIREVE-173 > Project: Directory Server > Type: Bug > Components: jdbm database, jndi-provider > Versions: 0.9.1 > Reporter: Alex Karasulu > Assignee: Trustin Lee > Priority: Blocker > > I changed the name of an entry like ou=Users, dc=example, dc=com to ou=users, > dc=example, dc=com which had a single ou=Users. I expected this operation to > delete the old attribute rather then just add the new one. This can become a > serious issue hence the reason why its a blocker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
