Hi Aaron, You're right. The SQL parser is very sensitive to spaces in general. We're working to the new parser much faster and accurate. It will be released in beta in 2.1.
Lvc@ On 5 December 2014 at 18:17, Aaron Schulz <[email protected]> wrote: > <<select id from Item where pids contains(625) limit 10 TIMEOUT 3000>> is > fast but having "contains (625)" is slow and doesn't use an index. This is > with 1.7.10. It took me a while to track this down. > > The index can be: > create index ItemPidsIdx on Item (pids,id) notunique; > > ...or even just: > create index ItemPidsIdx on Item (pids) notunique; > > Either way this seems to happen. With millions of rows, the whitespace > version times out. > > The full Item class is: > > create class Item extends V; > create property Item.id long; > create property Item.sitelinks EMBEDDEDSET string; > create property Item.pids EMBEDDEDSET long; > create property Item.pids_someval EMBEDDEDSET long; > create property Item.pids_noval EMBEDDEDSET long; > create index ItemIdIdx on Item (id) unique; > create index ItemSiteLinksIdx on Item (sitelinks) notunique_hash_index; > create index ItemPidsIdx on Item (pids,id) notunique; > create index ItemPidsSomeValIdx on Item (pids_someval,id) notunique; > create index ItemPidsNoValIdx on Item (pids_noval,id) notunique; > > -- > > --- > 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.
