From 6f5bfd94a31139615e456d4e20804e8ed44b5a4a Mon Sep 17 00:00:00 2001 From: Wilfried Goesgens Date: Mon, 23 May 2016 15:20:29 +0200 Subject: [PATCH] We now need to specify _from and _to for edges, since they're part of the regular document now and mandatory. --- .../Books/Users/Graphs/GeneralGraphs/Management.mdpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/Books/Users/Graphs/GeneralGraphs/Management.mdpp b/Documentation/Books/Users/Graphs/GeneralGraphs/Management.mdpp index 28fdbf0665..3c6abf24ba 100644 --- a/Documentation/Books/Users/Graphs/GeneralGraphs/Management.mdpp +++ b/Documentation/Books/Users/Graphs/GeneralGraphs/Management.mdpp @@ -849,7 +849,7 @@ the edge will not be stored. -Replaces the data of an edge in collection edgeCollectionName +Replaces the data of an edge in collection edgeCollectionName. Note that `_from` and `_to` are mandatory. `graph.edgeCollectionName.replace(edgeId, data, options)` @@ -869,7 +869,7 @@ Replaces the data of an edge in collection edgeCollectionName var examples = require("@arangodb/graph-examples/example-graph.js"); var graph = examples.loadGraph("social"); graph.relation.save("female/alice", "female/diana", {typo: "nose", _key: "aliceAndDiana"}); - graph.relation.replace("relation/aliceAndDiana", {type: "knows"}); + graph.relation.replace("relation/aliceAndDiana", {type: "knows", _from: "female/alice", _to: "female/diana"}); ~ examples.dropGraph("social"); @END_EXAMPLE_ARANGOSH_OUTPUT @endDocuBlock generalGraphEdgeCollectionReplace