Re: Problems with EQUALITY generalizedTimeMatch

[Jon Roberts <man@mentata.com>]

Try an ORDERING clause to your attribute definitions, like:

ORDERING numericStringOrderingMatch

See also:

http://www.openldap.org/doc/admin22/schema.html#Extending%20Schema

which I notice doesn't list the generalizedTimeMatch syntax.

Jon Roberts
www.mentata.com

Thomas Stinner wrote:
> attributetype ( 1.3.6.1.4.1.11048.1.1.1.4
>         NAME 'vacationStart'
>         SINGLE-VALUE
>         SYNTAX 1.3.6.1.4.1.1466.115.121.1.24
>         DESC 'Beginning of vacation'
>         EQUALITY generalizedTimeMatch )

> 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 )