Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <1411071635.1123767899778.JavaMail.jira@ajax.apache.org>
Date: Thu, 11 Aug 2005 15:44:59 +0200 (CEST)
From: "Stefan Zoerner (JIRA)" <directory-dev@incubator.apache.org>
To: dev@directory.apache.org
Subject: [jira] Updated: (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

     [ http://issues.apache.org/jira/browse/DIREVE-173?page=all ]

Stefan Zoerner updated DIREVE-173:
----------------------------------

    Attachment: modRdn.ldif

I have attached  an LDIF example for the first case.

I applied it to a test server (IBM Tivoli Directory Server) and the result (after both modrdn) is:

dn: cn=Myra E. Amos,dc=example,dc=com
objectclass: top
objectclass: person
cn: Myra Ellen Amos
cn: Myra E. Amos
sn: Amos
description: an American singer-songwriter

I think behaviour is logical. The first modrdn adds a value to cn and does not delete the old value of the cn.
Therefore, Tori has two values for attribute cn after the first modrdn, one of them forms the rdn "cn=Tori Amos", the other "cn=Myra Ellen Amos" does not (cn allows multiple values).

The second operation adds a new value for cn ("cn=Myra E. Amos"), uses it as the new rdn, and deletes the attribute value of the old rdn ("cn=Tori Amos").
As a consequence, the attribute value "cn=Tori Amos" is gone, but "cn=Myra Ellen Amos", which was not part of the rdn not.

The point here is that cn allows multiple values. Behavior is different otherwise.


> 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: jndi-provider, jdbm database
>     Versions: 0.9.1
>     Reporter: Alex Karasulu
>     Assignee: Trustin Lee
>     Priority: Blocker
>  Attachments: modRdn.ldif
>
> 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