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: <1115865483.1255363711317.JavaMail.jira@brutus>
Date: Mon, 12 Oct 2009 09:08:31 -0700 (PDT)
From: "Stefan Seelmann (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Resolved: (DIRSTUDIO-513) Do delete before add when
 modifying attribute values
In-Reply-To: <960974446.1249565835041.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DIRSTUDIO-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seelmann resolved DIRSTUDIO-513.
---------------------------------------

    Resolution: Fixed
      Assignee: Stefan Seelmann

Fixed in trunk:
  http://svn.apache.org/viewvc?rev=824365&view=rev


> Do delete before add when modifying attribute values
> ----------------------------------------------------
>
>                 Key: DIRSTUDIO-513
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-513
>             Project: Directory Studio
>          Issue Type: Improvement
>    Affects Versions: 1.4.0
>            Reporter: Martin Alderson
>            Assignee: Stefan Seelmann
>            Priority: Minor
>             Fix For: 1.5.0
>
>
> When connecting to Novell eDirectory and modifying the schema an "Attribute Or Value Exists" error occurs.  This is due to the modification performing an add before the delete and eDirectory (wrongly) complains that the same OID has been used more than once before realising that the old value should be deleted.  Note that this is a problem with eDirectory but it would be useful if Studio asked for the delete to be performed before the add when modifying an attribute value which eDirectory is OK with.
> An example of the LDIF in the modifications logs view for an operation that fails is:
> dn: cn=schema
> changetype: modify
> add: objectClasses
> objectClasses: ( 2.16.840.1.113730.3.2.2 NAME 'inetOrgPerson' [...new value...]
> -
> delete: objectClasses
> objectClasses: ( 2.16.840.1.113730.3.2.2 NAME 'inetOrgPerson' [...old value...]
> -
> It also seems that modifying the schema on ApacheDS has the same issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.