RE: [ISSUE?] : jpegPhoto, EQUALITY, octetStringMatch (OL 2.1.17)

["Kirill Kovalenko" <kirill@softerra.com>]

of course we can use such a tricks - but it would be really expensive operation, especially in case of jpegPhoto.

-
Kirill

> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org 
> [mailto:owner-openldap-software@OpenLDAP.org] On Behalf Of 
> Michael Strцder
> Sent: Wednesday, May 21, 2003 3:49 PM
> To: Hallvard B Furuseth
> Cc: Kirill Kovalenko; openldap-software@OpenLDAP.org
> Subject: Re: [ISSUE?] : jpegPhoto, EQUALITY, octetStringMatch 
> (OL 2.1.17)
> 
> 
> Hallvard B Furuseth wrote:
> > Kirill Kovalenko writes:
> > 
> >>We've noticed that it's impossible to perform entry modification for
> >>jpegPhoto attribute. Its schema definition has no EQUALITY
> >>specification (...)
> > 
> > You can use LDAP_MOD_REPLACE which  deletes the old value 
> and inserts
> > the new one.  This does not need an equaltiy matching rule.
> 
> One can also remove the whole attribute with LDAP_MOD_DELETE 
> by specifying 
> attribute type (without specifying certain attribute value) 
> and re-add the 
> whole attribute with all updated attribute values using 
> LDAP_MOD_ADD, all in 
> one ModifyRequest.
> 
> What I've learned this seems to be more robust in general 
> with many LDAP 
> servers than using LDAP_MOD_REPLACE (e.g. when updating sub 
> schema sub entry 
> of Netscape 4.x directory server).
> 
> Ciao, Michael.
>