Re: LDAP filter problem

[Raf Meeusen <Raf.Meeusen@wooble.BE>]

Branko,

Does (someattribute=100) returns something?  It should do that, because
you've a EQUALITY numerricStringMatch.  However, I don't see any
ORDERING keyword, so you can't make a filter like <= or >=...

If you want to have the <=, <=, < and > options, you'll have to extend
your schema with ORDERING...

Indexing is just a way of speeding things up.  It isn't evil.  The only
other possible problem are you're ACL's.  I assume you have enough
permissions to access the data?

kr,

Raf

On Mon, 2003-04-07 at 21:41, Branko F. Gracnar wrote:
> > Use this one: (somattribute>=100)
> 
> it doesn't return any object at all :(
> 
> attrubute definition
> 
> attributetype ( 1.1.1.1.9 NAME 'someattribute'
>         SINGLE-VALUE
>         DESC 'A flag, signalling if the corresponding user is on vacation
> right now'
>         SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{1}
>         EQUALITY numericStringMatch )
> 
> 
> > For more details please turn to the RFC2254
> I've read entire RFC today, that's why i'm very suprised why this is not
> working...
> 
> attrubute 'someattribute' is indexed too. May this be root of all evil ? :)
> 
> slapd.conf:
> index           someattribute  eq
> 
> Brane
-- 
Raf Meeusen <Raf.Meeusen@wooble.BE>