[DIRSTUDIO-513] Do delete before add when modifying attribute values

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.5.0
• Component/s: studio-ldapbrowser
• Assignee: Stefan Seelmann
• Reporter: Martin Alderson
• Created: 06/Aug/09 13:36
• Updated: 19/Nov/09 15:43
• Resolved: 12/Oct/09 16:06

Description

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.