Re: Index on createTimestamp and modifyTimestamp

[Harry Rüter <harry_rueter@gmx.de>]

Hi,

if i remember right ">" isn't implemented (in LDAP, not only openldap).
Try 
"!(modifyTimestamp<=20020718000000Z)" 
instead, which has the same meaning.

greets Harry

Allan Streib wrote:
> 
> Any update on this?  I can (in 2.0.23) do a search filter like:
> 
> (modifyTimestamp=20020718214640Z)
> 
> and that works but:
> 
> (modifyTimestamp>20020718000000Z)
> 
> returns "bad search filter"
> 
> Is there another way to identify entries that have been modified after
> a given time?
> 
> Allan
> 
> On Fri, 8 Mar 2002, Hul van den, G (Gerrit) wrote:
> 
> >
> > Hi all,
> >
> > I have to do a search on createTimestamp and modifyTimestamp. These
> > attributes are not indexed.
> >
> > At this time, is is not allowed to build an index on the createTimestamp and
> > modifyTimestamp. (Still true?)
> >
> > I have checked the schema. The createTimestamp gives for EQUALITY
> > generalizedTimeMatch and for ORDERING generalizedTimeOrderingMatch. These
> > matches are not implemented yet. (Also still true?)
> >
> > Isn't is possible to change this to a simple CaseExactMatch /
> > CaseIgnoreOrderingMatch or is this not possible for some reason?
> >
> > Greetings,
> >
> > Gerrit van den Hul
> >