directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leo Bergolth (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSTUDIO-513) Do delete before add when modifying attribute values
Date Fri, 21 Aug 2009 14:31:14 GMT

    [ https://issues.apache.org/jira/browse/DIRSTUDIO-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745992#action_12745992
] 

Leo Bergolth commented on DIRSTUDIO-513:
----------------------------------------

I am currently facing similar problems when trying to modify openldap's
runtime configuration: Many attributes like olcDbConfig don't have
equality matching rules, therefore delete/add modifications won't work.

So at least offering an option to do replace modifications instead of
add/delete even on multi-valued attributes would be really useful.


> 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
>            Priority: Minor
>
> 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.


Mime
View raw message