directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seelmann (JIRA)" <>
Subject [jira] Commented: (DIRSTUDIO-513) Do delete before add when modifying attribute values
Date Mon, 12 Oct 2009 16:06:31 GMT


Stefan Seelmann commented on DIRSTUDIO-513:

@Quanah: Thanks for the pointer. I also tested with hidden schema. In that case Studio falls
back to a built-in default schema (that is derived from OpenLDAP and contains all the standard
schema objects). However I wonder if this makes really sense. When the server really uses
standard schema this approach works fine. However if there are custom schema elements Studio
can't guess which attributes are allowed or required and pops up wrong warnings. So my idea
is to remove this default schema and to disable all the schema checks if no schema is present.
Thanks again.

> Do delete before add when modifying attribute values
> ----------------------------------------------------
>                 Key: DIRSTUDIO-513
>                 URL:
>             Project: Directory Studio
>          Issue Type: Improvement
>    Affects Versions: 1.4.0
>            Reporter: Martin Alderson
>            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' [ 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.

View raw message