Hi Emil, Traverse was implemented this way to avoid infinite loops, but now we know it's a limitation and we are thinking about a finer strategy, where the user can define (per single query) how traversed nodes have to be considered: - skip traversed nodes globally - skip traversed nodes in current path - never skip - other...
This feature is not tracked yet in the issue tracker, could you please open an issue about this? Thanks Luigi 2015-06-01 14:58 GMT+02:00 Emin Agassi <emin.agassi...@gmail.com>: > Hello All > I am traversing a Graph that has some common Vertices. When I execute > traverse, I only see one instance of the common Vertix versus several. > For example, > > A -> B > C -> B > > After traverse, I only see the following result: > > A > C > B (common and pointed to by A and C) > > I would like to see the duplicate Vertix in the result as follows: > > A > B (Common to A and C) > C > B (Common to A and C) > > Is there a method to achieve this or Traverse always returns Distinct > Vertices? > > Thank you > Emin > > > -- > > --- > 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 orient-database+unsubscr...@googlegroups.com. > 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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
