[Date Prev][Date Next] [Chronological] [Thread] [Top]

Add values without equality matching rule



[Protocol] 4.6 (Modify Operation) says:

   If an EQUALITY matching rule has not been defined for an attribute 
   type, clients MUST NOT attempt to add or delete individual values of 
   that attribute from an entry using the "add" or "delete" form of a 
   modification, and MUST instead use the "replace" form. 

Why not?  What's the difference between adding values one at a time and
all at once?  The server has to compare them in any case, to check that
two equivalent values are not added.  If there is no equality matching
rule, it compares the values octet by octet.  (See [Models] 2.3.)

-- 
Hallvard