Another suggestion, try using PlayerID instead of PlayerId (Case-sesitive).
On Friday, 5 June 2015 14:34:00 UTC+5:30, MV-dev1 wrote: > > Thanks Kapil for the quick reply. That would make sense if the index was > corrupted but that didn't fix it for me. > > I rebuilt the index in studio and tried my query again but it still > behaves the same. > > The query with the range returns correctly and the one that would likely > use the index does not. > > On Friday, June 5, 2015 at 11:58:35 AM UTC+3, Kapil Ranade wrote: >> >> I faced similar problem.. Just try re-building indexes. >> >> -- --- 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.
