Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CF8B818B6E for ; Tue, 19 May 2015 14:43:03 +0000 (UTC) Received: (qmail 90177 invoked by uid 500); 19 May 2015 14:43:03 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 90124 invoked by uid 500); 19 May 2015 14:43: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 90050 invoked by uid 99); 19 May 2015 14:43:02 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2015 14:43:02 +0000 Date: Tue, 19 May 2015 14:43:02 +0000 (UTC) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FC-13) DAO Updates enhancement MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FC-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lecharny updated FC-13: -------------------------------- Fix Version/s: (was: 1.0.0-RC40) 1.0.0-RC41 > DAO Updates enhancement > ----------------------- > > Key: FC-13 > URL: https://issues.apache.org/jira/browse/FC-13 > Project: FORTRESS > Issue Type: Improvement > Environment: all > Reporter: Emmanuel Lecharny > Assignee: Emmanuel Lecharny > Fix For: 1.0.0-RC41 > > > 09:15:48 AM emmanuel lecharny: I may have a few q regarding the update methods > 09:16:08 AM emmanuel lecharny: it seems that you remove an Attribute before adding some new values > 09:18:43 AM emmanuel lecharny: something like : > 09:18:44 AM emmanuel lecharny: LDAPModification(type=replace, attr=ftRoles, values={}), > LDAPModification(type=add, attr=ftRoles, values= > {'oamT10SSDR1'})] > 09:19:16 AM emmanuel lecharny: which results in two modification bing done on the entry, instead of one > 09:19:22 AM emmanuel lecharny: not a big deal though > 09:19:47 AM emmanuel lecharny: I assume that all the ftRoles get removed first, then you inject one new one > 09:20:06 AM * emmanuel lecharny out for 5 mins > 09:33:24 AM smckinney: so you are saying two roundtrips for those operations? > 09:34:22 AM smckinney: the intent is yes to replace the old with the new > 09:40:49 AM emmanuel lecharny: smckinney: no, this will be done in one single rountrip. This is why t's not a big deal > 09:41:00 AM smckinney: yes that was my assumption as well > 09:41:16 AM smckinney: but having your eyes in there will be good > 09:42:23 AM smckinney: how would you have done this? > 09:44:55 AM emmanuel lecharny: a replace with thevalues will blank the existing data, and inject the added values > 09:45:10 AM emmanuel lecharny: so no eed to do LDAPModification(type=replace, attr=ftRoles, values={}), > 09:45:39 AM emmanuel lecharny: doing LDAPModification(type=replace, attr=ftRoles, values={'oamT10SSDR1'} > )] should be enough > 09:46:27 AM smckinney: yes agreed. wondering why I did not do that to begin with... > 09:47:28 AM smckinney: will create an issue to take another look at it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)