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

Attributes without matching rules in 2.0 schema


There are several attributeTypes in the schema for 2.0 which don't have
matching rules and are not single valued. For example, in core.schema:

attributetype ( NAME ( 'facsimileTelephoneNumber' 'fax' )

This causes a problem in that it is not possible to delete a specific value
from this attribute. Without a matching rule, attempting to do this causes
error 18 "Inappropriate Matching".

What to do? I don't want to modify standard schema items (but for testing
that's what I have done - by adding matching rules). I could use "replace"
to get the same effect, but I'd like to be able to use the same method to
manage ALL attributeTypes, and using "replace" on say groups with 100's of
members is not a good option. Also we have LDAP management software working
fine with OpenLDAP 1. using the "delete specified value" method, and don't
want to change it just for selected attributeTypes in 2.0.

My immediate reaction is that the standard schema items are incompletely
defined -
maybe someone with more expertise than me could comment on why they look
this way? And if they should be changed to include matching rules?