[Date Prev][Date Next]
Re: HowTo index generalizedTimeOrderingMatch
Thanks for *both* advices, that helped me a lot!
2012/5/4 Michael Ströder <firstname.lastname@example.org>:
> Hallvard Breien Furuseth wrote:
>> On Fri, 4 May 2012 14:13:38 +0200, Meike Stone wrote:
>>> attributetype (220.127.116.11.4....
>>> NAME ('InsertTime')
>>> EQUALITY generalizedTimeMatch
>>> ORDERING generalizedTimeOrderingMatch
>>> SYNTAX 18.104.22.168.4.1.1422.214.171.124.24
>>> Now I can use this and search, but it takes very long.
>>> So I want index it for searching:
>>> * greater (">=")
>>> * less ("<=")
>> Use an eq index. This doubles as an ordering index for some non-string
>> syntaxes, including integer, generalizedTime, and (I think) CSN.
> I brought up this discussion before:
> In case the range filter is combined with a another indexed filter the
> eq-index can even lead to slower searches.
> Ciao, Michael.