Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
all
Description
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=
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.