Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 15666 invoked from network); 23 May 2007 22:06:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 May 2007 22:06:41 -0000 Received: (qmail 88937 invoked by uid 500); 23 May 2007 22:06:46 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 88895 invoked by uid 500); 23 May 2007 22:06:46 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 88876 invoked by uid 99); 23 May 2007 22:06:46 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 May 2007 15:06:46 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 May 2007 15:06:39 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id DC919714058 for ; Wed, 23 May 2007 15:06:18 -0700 (PDT) Message-ID: <25226361.1179957978901.JavaMail.jira@brutus> Date: Wed, 23 May 2007 15:06:18 -0700 (PDT) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Subject: [jira] Resolved: (DIRSTUDIO-109) Schema Entry Deletes Must be Sequenced In-Reply-To: <27322535.1179947956334.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DIRSTUDIO-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lecharny resolved DIRSTUDIO-109. ----------------------------------------- Resolution: Invalid As explain by Alex, this is the intended behavior > Schema Entry Deletes Must be Sequenced > -------------------------------------- > > Key: DIRSTUDIO-109 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-109 > Project: Directory LDAP Studio > Issue Type: New Feature > 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.955495751 cannot 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.955495751 cannot 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.