Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 27979 invoked from network); 17 Sep 2008 17:36:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Sep 2008 17:36:06 -0000 Received: (qmail 19238 invoked by uid 500); 17 Sep 2008 17:36:02 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 19193 invoked by uid 500); 17 Sep 2008 17:36:02 -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 19182 invoked by uid 99); 17 Sep 2008 17:36:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Sep 2008 10:36:02 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Sep 2008 17:35:12 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 8ADD8234C1D6 for ; Wed, 17 Sep 2008 10:35:44 -0700 (PDT) Message-ID: <1962790248.1221672944567.JavaMail.jira@brutus> Date: Wed, 17 Sep 2008 10:35:44 -0700 (PDT) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Subject: [jira] Commented: (DIRSERVER-840) Double modification on a modify ? In-Reply-To: <19233885.1170459485779.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/DIRSERVER-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631860#action_12631860 ] Emmanuel Lecharny commented on DIRSERVER-840: --------------------------------------------- I just wonder why an operationnal attribute is checked against the schema ??? This sounds like a nonsense, as Op attr are managed by the server itself, so they are just always valid ! > Double modification on a modify ? > --------------------------------- > > Key: DIRSERVER-840 > URL: https://issues.apache.org/jira/browse/DIRSERVER-840 > Project: Directory ApacheDS > Issue Type: Improvement > Affects Versions: 1.5.1 > Reporter: Emmanuel Lecharny > Assignee: Emmanuel Lecharny > Fix For: 1.5.5 > > > We have had a convo with alex about the OperationalService. I saw that when doing a modification on an entry, we first call the next interceptor (and this will modify the entry on the backend), then we add two new attributes (modifiers name and date) and store again the data into the backend. This does not seems to be very efficient, but we don't remember the reason why it's done like that ... > Here is the convo > elecharny in OperationalService > akarasulu yep > elecharny when doing a modify, > akarasulu ahha > elecharny you first call the next interceptor, then you update the nexus with the entry with > elecharny two new attributes > elecharny why don't you add the attrs into the entry and then call the netx interceptors ? > akarasulu hmmm I had some reason for this > elecharny this is a simple modify instead of two > akarasulu don't remember > akarasulu yeah yeah I see what you mean > akarasulu can't remember now > elecharny this seems to cost the double > akarasulu yes it does > akarasulu can you put this in JIRA > elecharny yeah > akarasulu just past this info > akarasulu from IRC -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.