Hi group,
While I'm already looking at other query patterns (e.g. using LINKS <https://groups.google.com/forum/#!topic/orient-database/GEVJ9Ba2848>) I would like to ask what the experiences are with extensive OR queries in OrientDB. I know many traditional databases have a lot of trouble with "WHERE ... IN [ ... large collection ... ]" kind of queries. I'm seeing similarly slow results with my tests, such as: ... WHERE ... AND permissionNodeId IN [1, 2, 6, 12, 12064, 19614, 19742, 19863, 21453, 21454, 21457, 21657, 21658, 31123, 31127, 31130, 47691, 55603, 55650, 56026, 56028, 56029, 56050, 56052, 85383, 85406, 85615, 105665, 1035242, 1035243] AND ... This particular query takes around 2~3 seconds, which is just not good enough for our application. I have added some indices, among which a NOTUNIQUE_HASH_INDEX on permissionNodeId, which is typed as LONG. Is there other strategies to follow here? Other indexing strategies? Using a graph equivalent of this (I don't see how that removes the need for an IN query)? Thanks for your help. Sander. -- --- 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.
