Hi, you can do: traverse out() from parent while $depth < 10
Without the while condition you risk to have huge traversals. Best Regards, Luca Garulli CEO at Orient Technologies LTD the Company behind OrientDB http://about.me/luca.garulli On 24 April 2015 at 21:20, Jeffrey Miller <[email protected]> wrote: > I think I found the answer to my last question in the Udemy course- no, I > would need to chain out() calls to the desired depth. > > How would I use traverse to do the same thing but up to an arbitrary depth > where I want the response to be the nodes? > > Thanks for your help! > > > On Friday, April 24, 2015 at 3:11:32 PM UTC-4, Jeffrey Miller wrote: >> >> Thanks, I will give that I try. >> >> Is there a general rule of thumb for traverse vs select? Will select >> automatically recursively keep traversing relationships? >> >> On Friday, April 24, 2015 at 10:30:35 AM UTC-4, l.garulli wrote: >>> >>> Hi Jeffrey, >>> It's simpler: >>> >>> *select out() from parent* >>> >>> retrieves the outgoing collection. If you want that vertices as result, >>> use the expand: >>> >>> *select expand( out() ) from parent* >>> >>> Lvc@ >>> >>> >>> >>> >>> On 24 April 2015 at 16:20, Jeffrey Miller <[email protected]> wrote: >>> >>>> Is there up to date documentation about how to use traverse for the >>>> Graph mode? I been trying to do a very simple query looking for the nodes >>>> that are connected by an edge to a parent node ( parent ---E---> child) , >>>> and I have seen 3 different ways to do this >>>> >>>> traverse V.out, E.in from parent >>>> traverse out() from parent >>>> traverse out_edge_name from parent >>>> >>>> The last two seem to work, but I think its giving me the edges, not the >>>> connected nodes themselves. I suspect I need to use the expand function, >>>> but I am not sure. Any hints on the correct way to do graph traversal >>>> (perhaps this would better be executed with a select?) or pointers to >>>> documentation would be greatly appreciated. >>>> >>>> Thanks! >>>> >>>> On Friday, December 12, 2014 at 7:17:23 AM UTC-5, Andrei Serea wrote: >>>>> >>>>> I think I figured out how to go around the size limit of the query in >>>>> Graph editor: >>>>> When I write the query directly in the Graph Editor, I cannot set the >>>>> limit, as I can in the Browse section. And I think it is implicitly set to >>>>> 20. >>>>> If, however I write the same query in the Browse , set the limit to >>>>> 200 and then do "Send to Graph", I see the entire result. >>>>> >>>>> Andrei >>>>> >>>> -- >>>> >>>> --- >>>> 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. >>>> >>> >>> >>> >>> -- >>> Best Regards, >>> >>> Luca Garulli >>> CEO at Orient Technologies LTD >>> the Company behind OrientDB >>> http://about.me/luca.garulli >>> >>> -- > > --- > 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.
