On May 26, 2010, at 11:10 PM, Howard Chu wrote:
> Ludovic Poitou wrote:
>> Are you really trying to achieve a MOD_ADD_IF_NOT_PRESENT or don't fail
> adding an attribute or value if the value is already present ?
>>
>> MS AD has a PERMISSIVE MODIFY CONTROL that remove the ADD/DELETE
>> constraint
>
> On May 26, 2010, at 11:10 PM, Howard Chu wrote:
>
>> Ludovic Poitou wrote:
>>> Are you really trying to achieve a MOD_ADD_IF_NOT_PRESENT or don't fail
>> adding an attribute or value if the value is already present ?
>>>
>>> MS AD has a PERMISSIVE MODIFY CONTROL that remove the ADD/DELETE
>>> c
> Do you have a use case for this? I'm implementing add-if-not-present to
> ease the implementation of the version number overlay, so I could
> implement softdel as well.
>
> I think all of these could make sense also protocol-wise (including
> softadd), but I'm not in the mood right now to start
>> Do you have a use case for this? I'm implementing add-if-not-present to
>> ease the implementation of the version number overlay, so I could
>> implement softdel as well.
>>
>> I think all of these could make sense also protocol-wise (including
>> softadd), but I'm not in the mood right now to
>>> Soft Del: The attribute shall contain none of these values, but might
>>> have
>>> others
>
>> I'm not sure I understand how SOFTDEL differs from LDAP_MOD_DELETE. Do
>> you mean that values listed in SOFTDEL will be deleted if they exist, or
>> otherwise ignored?
>
> Yes; LDAP_MOD_DELETE requi
Ludovic Poitou wrote:
Are you really trying to achieve a MOD_ADD_IF_NOT_PRESENT or don't fail
adding an attribute or value if the value is already present ?
MS AD has a PERMISSIVE MODIFY CONTROL that remove the ADD/DELETE
constraints
on the attributes and values, so that adding an attribute t
>> Soft Del: The attribute shall contain none of these values, but might have
>> others
> I'm not sure I understand how SOFTDEL differs from LDAP_MOD_DELETE. Do
> you mean that values listed in SOFTDEL will be deleted if they exist, or
> otherwise ignored?
Yes; LDAP_MOD_DELETE requires that the
>>> Soft Del: The attribute shall contain none of these values, but might
>>> have
>>> others
>
>> I'm not sure I understand how SOFTDEL differs from LDAP_MOD_DELETE. Do
>> you mean that values listed in SOFTDEL will be deleted if they exist, or
>> otherwise ignored?
>
> Yes; LDAP_MOD_DELETE requi
> Are you really trying to achieve a MOD_ADD_IF_NOT_PRESENT or don't fail
> adding an attribute or value if the value is already present ?
>
> MS AD has a PERMISSIVE MODIFY CONTROL that remove the ADD/DELETE
> constraints on the attributes and values, so that adding an attribute that
> exist will s
Are you really trying to achieve a MOD_ADD_IF_NOT_PRESENT or don't fail adding
an attribute or value if the value is already present ?
MS AD has a PERMISSIVE MODIFY CONTROL that remove the ADD/DELETE constraints on
the attributes and values, so that adding an attribute that exist will succeed
b
>> I need to implement a modify operation whose semantics is "add if not
>> present", an add that only takes place if that attribute is not yet
>> present in the entry.
>>
>> I need it as an internal operation, so right now I wouldn't bother
>> formalizing it as an extension of the semantics of the
> I need to implement a modify operation whose semantics is "add if not
> present", an add that only takes place if that attribute is not yet
> present in the entry.
>
> I need it as an internal operation, so right now I wouldn't bother
> formalizing it as an extension of the semantics of the modi
> masar...@aero.polimi.it wrote:
>> I need to implement a modify operation whose semantics is "add if not
>> present", an add that only takes place if that attribute is not yet
>> present in the entry.
>>
>> I need it as an internal operation, so right now I wouldn't bother
>> formalizing it as an
masar...@aero.polimi.it wrote:
I need to implement a modify operation whose semantics is "add if not
present", an add that only takes place if that attribute is not yet
present in the entry.
I need it as an internal operation, so right now I wouldn't bother
formalizing it as an extension of the
14 matches
Mail list logo