Skip to content

Commit 6c8e7ab

Browse files
authored
DOC-2112-fix-delete-edge-EBNF-3.8
1 parent e17a651 commit 6c8e7ab

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

modules/ddl-and-loading/pages/creating-a-loading-job.adoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -1104,7 +1104,7 @@ CREATE LOADING JOB abc FOR GRAPH Graph_Name {
11041104
DELETE VERTEX vertex_type_name (PRIMARY_ID id_expr) FROM f [WHERE condition] ;
11051105
11061106
// Delete each edge which has the given edge type, source vertex id, target vertex id, and discriminator value if provided.
1107-
DELETE EDGE edge_type_name (FROM id_expr, TO id_expr, DISCRIMINATOR (id_expr)) FROM f [WHERE condition] ;
1107+
DELETE EDGE edge_type_name (FROM id_expr, TO id_expr[, DISCRIMINATOR (id_expr)] ) FROM f [WHERE condition] ;
11081108
11091109
// Delete all edges which have the given edge type and source vertex id. (Destination vertex id is left open.)
11101110
DELETE EDGE edge_type_name (FROM id_expr) FROM f [WHERE condition] ;
@@ -1145,4 +1145,4 @@ DELETE EDGE Study_At (from $"person_id", to $"university_id",
11451145
====
11461146
There is a separate DELETE statement in the GSQL Query Language. The query delete statement can leverage the query language's ability to explore the graph and to use complex conditions to determine which items to delete.
11471147
In contrast, the loading job delete statement requires that the id values of the items to be deleted must be specified in advance in an input file.
1148-
====
1148+
====

0 commit comments

Comments
 (0)