Hi Mahigu, for sure these are examples on very small data sets, so a human can easily grasp the iterations the graph engine is going to take.
Graphs can be compared with pivot tables in SQL (see https://docs.arangodb.com/2.8/Graphs/index.html ) that overcome the limit that you need to code each hop you are going to take. In general you should rather use the new pattern matching traversals: https://docs.arangodb.com/2.8/Aql/GraphTraversals.html If these parts of the documentation don't make clear what graphs are for, please rephrase your question along with what you read there. Cheers, Willi On Monday, May 30, 2016 at 3:47:56 PM UTC+2, [email protected] wrote: > > Hi All, > > I couldn't understand the necessity of creating graphs in ArangoDB. > > For example, refer the below AQLs, > > *// Paths between 2 vertices* >> >> FOR p IN TRAVERSAL(person, knows, "person/person3", "outbound", { paths: >> true, filterVertices: [{_id: "person/person2"}], vertexFilterMethod: >> ["exclude"]}) >> >> RETURN p.path.vertices[*].name >> >> >> >> *//All connected Vertices for a given Vertex..* >> >> FOR p IN PATHS(person, knows, "outbound") >> >> FILTER p.source._id == "person/person5" >> RETURN p.vertices[*].name > > > > The above two queries are clearly related to Graphs...but you no need to > create a graph to make them work. > > Then why should i create a graph? > > What advantages will i get if i create a graph? > > when to create a graph and when not to (I mean in what scenarios creating > Graphs will help) ? > > I'm totally confused. Please help me in understanding this. > > Thanks & Best Regards, > - Mahi > -- You received this message because you are subscribed to the Google Groups "ArangoDB" 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.
