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

postalAddress / CaseIgnoreListMatch (ITS#2614)

Full_Name: Jeremy Scott
Version: 2.1.19
OS: Solaris 8
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (

Alright here goes...

I guess this is also a 'feature' request more than a bug report 
but it could be both.

I'm not sure when, but sometime recently, EQUALITY for 
the postalAddress schema has changed from 'caseIgnoreMatch'
to 'caseIgnoreListMatch' 

While I'm not sure why this is, it does pose a problem for
programs which have previously relied on the old definition.

I have a program which will attempt to delete the the postalAddress
of an entry in a modify operation. It fails because it specifies
the value it wants to delete. (Not allowed by the new EQUALITY 

However, there is only one value in LDAP and that is exactly the 
value I specified to delete. Why should this be an error? Strictly
speaking, it's violating the rules, but why does that rule
have to apply when there is only one value for the attribute? 
Technically, I am matching the list....

Previous EQUALITY definition for 'postalAddress'
(iPlanet DS 4.x - 5.1, Older OpenLDAP)
( NAME 'caseIgnoreMatch' SYNTAX ) 

OpenLDAP 2.1.19 core schema EQUALITY definition for 'postalAddress'
( NAME 'caseIgnoreListMatch' SYNTAX )