Hi, If you define a composite index for "out, in" on E class, your lookups will be much faster. However, check your model if you can avoid indexes by just crossing the edges. Example:
SELECT in()[@rid=#11:1820'].weight as weight FROM #11:12916 Best Regards, Luca Garulli Founder & CEO OrientDB <http://orientdb.com/> On 16 May 2016 at 11:57, K Major <[email protected]> wrote: > Indeed, thanks a lot ! > > I'm also wondering if there is a more efficient way to do this query ? > > I think it's not possible to define a index on the 'in' and 'out' fields ? > > Le lundi 16 mai 2016 08:07:44 UTC+2, scott molinari a écrit : >> >> The "out" property in vertex #11:1820 holds the rids to the edges it >> links to, not the rids to the other vertexes. You need the id of the other >> vertex as your "out" value in your query. >> >> Scott >> > -- > > --- > 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.
