On Tue, 2010-01-05 at 15:01 +0100, Pavel Zuna wrote:
> ldap2._generate_modlist now uses more sophisticated means to decide when to
> use
> MOD_ADD+MOD_DELETE instead of MOD_REPLACE. Before it did MOD_REPLACE only on
> attributes explicitly specified in ldap2._FORCE_REPLACE_ON_UPDATE_ATTRS. Now
Rob Crittenden wrote:
Pavel Zuna wrote:
ldap2._generate_modlist now uses more sophisticated means to decide
when to use MOD_ADD+MOD_DELETE instead of MOD_REPLACE. Before it did
MOD_REPLACE only on attributes explicitly specified in
ldap2._FORCE_REPLACE_ON_UPDATE_ATTRS. Now it does MOD_REPLACE
Pavel Zuna wrote:
ldap2._generate_modlist now uses more sophisticated means to decide when
to use MOD_ADD+MOD_DELETE instead of MOD_REPLACE. Before it did
MOD_REPLACE only on attributes explicitly specified in
ldap2._FORCE_REPLACE_ON_UPDATE_ATTRS. Now it does MOD_REPLACE for all
single value a
ldap2._generate_modlist now uses more sophisticated means to decide when to use
MOD_ADD+MOD_DELETE instead of MOD_REPLACE. Before it did MOD_REPLACE only on
attributes explicitly specified in ldap2._FORCE_REPLACE_ON_UPDATE_ATTRS. Now it
does MOD_REPLACE for all single value attributes and never