Hi Keith, We improved SQL engine to use index also with mixed OR conditions in 2.0-SNAPSHOT. Could you try it?
Lvc@ ᐧ On 10 October 2014 23:30, Keith Freeman <[email protected]> wrote: > Bump. Anybody know if this is a bug or just a design limitation? > > On Tuesday, October 7, 2014 8:59:58 AM UTC-6, Keith Freeman wrote: >> >> I created two indexes on the same class (which has about 100k records): >> >> 1. create index Widget.a on Widget (a) notunique >> 2. create index Widget.b on Widget (b) notunique >> >> >> Queries "select * from Widget where a='abc'" and "select * from Widget >> where b='xyz'" are now MUCH faster than before the indexes (as expected). >> But this query is no faster (still takes about 3 seconds): "select * from >> Widget where a='abc' OR b='xyz'". >> >> Is this a bug or just a current limitation? Is there any way to use >> indexes to speed up the OR query? >> >> FYI I get the same results using orient 1.6.4 and 2.0-M2, and the same >> results if I use a lucene index and query. >> > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
