Re: On-disk-format of back-mdb depends on LDAP syntax?

[Michael StrÃder <michael@stroeder.com>]

Michael StrÃder wrote:
> Example entry created with msTestAttributeType3 declared as Boolean:
> 
> dn: uid=test,dc=example,dc=com
> msTestAttributeType2: foo
> msTestAttributeType3: TRUE
> objectClass: account
> objectClass: msTestObjectClass2
> uid: test
> 
> After changing declaration of msTestAttributeType3 to e.g. SUP name this
> change results in noSuchAttribute(16):
> 
> dn: uid=test,dc=example,dc=com
> changetype: modify
> delete: msTestAttributeType3
> msTestAttributeType3: TRUE
> -
> add: msTestAttributeType3
> msTestAttributeType3: FALSE
> -
> 
> This modification works (not the missing delete value):
> 
> dn: uid=test,dc=example,dc=com
> changetype: modify
> delete: msTestAttributeType3
> -
> add: msTestAttributeType3
> msTestAttributeType3: FALSE
> -
> 
> It seems the normalized values are used when processing delete-by-value.

Just for the records:
If the attribute value is first stored as DirectoryString syntax and attribute
type is changed to Boolean syntax there does not seem to be a problem.

Ciao, Michael.