Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 27931 invoked from network); 9 Aug 2005 08:42:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Aug 2005 08:42:43 -0000 Received: (qmail 73563 invoked by uid 500); 9 Aug 2005 08:42:42 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 73373 invoked by uid 500); 9 Aug 2005 08:42:41 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 73360 invoked by uid 99); 9 Aug 2005 08:42:41 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Aug 2005 01:42:39 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id EEDE6E2 for ; Tue, 9 Aug 2005 10:42:38 +0200 (CEST) Message-ID: <179715845.1123576958977.JavaMail.jira@ajax.apache.org> Date: Tue, 9 Aug 2005 10:42:38 +0200 (CEST) From: "Stefan Zoerner (JIRA)" To: dev@directory.apache.org Subject: [jira] Commented: (DIREVE-173) On modifyRdn server now adds additional Rdn attribute In-Reply-To: <237068248.1119873237088.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ 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