Re: >= (greater or equal) and <= (lower or equal) operators in search filter

["Alexandre Garel" <garel.alexandre@agora.msa.fr>]

Quanah Gibson-Mount a écrit :

> --On Thursday, July 15, 2004 5:28 PM +0200 Alexandre Garel 
> <garel.alexandre@agora.msa.fr> wrote:
>
> > Hie,
> > according to RFC 2254, one can use >= and <= operators in a search 
> > filter.
> > When I try it on an attribute like uid and cn, with openldap ver 2.1.22
> > it does not return an error but a 0 results and in logs I can see
> > filter="(?=undefined)".
> > Is that because
> > - openldap ver 2.1.22 does not implement that part of RFC 2254. In this
> > case, does newer version do this (and which one) ? (although
> > http://www.openldap.org/lists/openldap-software/200208/msg00598.html
> > seems to tell it's already implemented).
> > - uid and cn have no ordering  ? In this case, what shall I add to the
> > schema to make use of these operators on an attribute ?
> > Thanks
>
>
> This doesn't answer your question, but:
>
> OpenLDAP-2.1.22 was a particularly broken release, I suggest moving 
> away from it.
>
> More to your question: Does the schema allow inequality filters on 
> those attributes?
>
> --Quanah

Ok, I finally looked in RFC 2252 and found that my attribute must have 
ORDERING caseIgnoreOrderingMatch. in their definition (which is not the 
case as I have standard definition).
Declaring the filter 'undefined' if it does not have the ORDER 
directive  is also part of the specification.
Thanks
Alex

> --
> Quanah Gibson-Mount
> Principal Software Developer
> ITSS/Shared Services
> Stanford University
> GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html