Hello,
One more question regarding the changing of the LDAP Schema without reimporting all the data.
Is it possible to add ORDERING clause to a schema definition without re-import ?
E.g.:
Changing
attributetype ( 1.3.6.1.4.1.11048.1.1.1.5 NAME 'vacationEnd' SINGLE-VALUE SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 DESC 'End of vacation' EQUALITY generalizedTimeMatch )
To:
attributetype ( 1.3.6.1.4.1.11048.1.1.1.5 NAME 'vacationEnd' SINGLE-VALUE SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 DESC 'End of vacation' EQUALITY generalizedTimeMatch ORDERING numericStringOrderingMatch )
To search for dates with >= and <= ?
Regards, Robert
------------------------------------------------------------------------ COMPUTER CONCEPT CC Computersysteme und Kommunikationstechnik GmbH Robert Heinzmann Wiener Str. 114 - 116 Email: heinzmann@cc-dresden.de 01219 Dresden Telefon: +49 (0)351/8 76 92-0 Telefax: +49 (0)351/8 76 92-99 Internet: http://www.cc-dresden.de ------------------------------------------------------------------------
At 04:55 AM 1/8/2007, Heinzmann, Robert wrote:
One more question regarding the changing of the LDAP Schema without reimporting all the data.
Is it possible to add ORDERING clause to a schema definition without re-import ?
Assuming the rule was appropriate for attribute syntax, yes. But the example you gave won't work (with or without re-import) as the rule (numericStringOrderingMatch) is inappropriate for the attribute syntax (generizedTime). generalizedTimeOrderingMatch is an appropriate rule for the generizedTime attribute syntax.
-- Kurt
openldap-software@openldap.org