directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu" <akaras...@apache.org>
Subject Re: [jira] Created: (DIRSTUDIO-109) Schema Entry Deletes Must be Sequenced
Date Wed, 23 May 2007 19:47:51 GMT
Ole,

This is not a bug.

The schema subsystem is just telling you that you cannot delete a syntax
that is currently in use by
an attribute.  You want cascade deletes? This will not work because you can
have more than one
attribute that depends on this syntax.

Say you have A1 and A2 which both depend on S1.  If you delete A1 and expect
a cascading delete of S1
then what do you do with A2?  This is why a cascade delete of dependencies
is not implemented.  I
recommend removing this JIRA since it just does not make sense.   See what I
mean by this example?

Alex

On 5/23/07, Ole Ersoy (JIRA) <jira@apache.org> wrote:
>
> Schema Entry Deletes Must be Sequenced
> --------------------------------------
>
>                  Key: DIRSTUDIO-109
>                  URL: https://issues.apache.org/jira/browse/DIRSTUDIO-109
>              Project: Directory LDAP Studio
>           Issue Type: Bug
>           Components: ldapstudio-browser
>     Affects Versions: 0.7.0
>          Environment: FC6
>             Reporter: Ole Ersoy
>             Priority: Minor
>
>
> Actually this is probably more of a new feature than a bug...
>
> I created a
> schema entry
> like this:
>
> ou=attributeTypes,cn=ecore, ou=schema
> ou=syntaxes, cn=ecore, ou=schema
>
> I have one attributeType entry
> that depends on a syntax entry,
> under
> ou=syntaxes, cn=ecore, ou=schema
>
> When I select the entry
> cn=ecore, ou=schema
> and do a delete I get this:
>
> Error while deleting entry
> [LDAP: error code 53 - failed to delete entry m-oid=
> 1.3.6.1.4.1.18060.4.98100505.1019857.4101539.5010251.6529753.1101991.0529799.955495751,ou=syntaxes,cn=ecore,ou=schema:
> The syntax with OID
> 1.3.6.1.4.1.18060.4.98100505.1019857.4101539.5010251.6529753.1101991.0529799.955495751cannot
be deleted until all entities using this syntax have also been
> deleted.  The following dependees exist: [
> 1.3.6.1.4.1.18060.4.98515110.5310256.9575156.5495150.9981025.4855551.2981009.98495457.4101
> ]]
>   [LDAP: error code 53 - failed to delete entry m-oid=
> 1.3.6.1.4.1.18060.4.98100505.1019857.4101539.5010251.6529753.1101991.0529799.955495751,ou=syntaxes,cn=ecore,ou=schema:
> The syntax with OID
> 1.3.6.1.4.1.18060.4.98100505.1019857.4101539.5010251.6529753.1101991.0529799.955495751cannot
be deleted until all entities using this syntax have also been
> deleted.  The following dependees exist: [
> 1.3.6.1.4.1.18060.4.98515110.5310256.9575156.5495150.9981025.4855551.2981009.98495457.4101
> ]]
>
> If I delete the entries in this sequence manually everything is fine:
> ou=attributeTypes,cn=ecore, ou=schema
> ou=syntaxes, cn=ecore, ou=schema
> cn=ecore, ou=schema
>
> So if the delete function has the intelligence
> to understand that it has to delete the syntaxes
> before it can delete attributeTypes, that would be cool.
>
> Cheers,
> - Ole
>
>
>
>
>
>
>
> --
> 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