You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we only support edge patterns with a single label. Again, it would be nice to support more complex edge patterns in queries. For now, users have to simulate multi-label edges by using composition in the edge definition body (given in the workaround below):
FROM
GRAPH MyGraph
(u1:User)-[:IS_FRIENDS_WITH|IS_BEST_FRIENDS_WITH]->(u2:User)
SELECT *;
must be written as:
WITH
GRAPH MyTemporaryGraph AS
VERTEX (:User)
PRIMARY KEY (user_id)
AS Users,
EDGE (:User)-[:IS_FRIENDS_OR_BEST_FRIENDS_WITH]->(:User)
SOURCE KEY (source_id)
DESTINATION KEY (dest_id)
AS (
<IS_FRIENDS_WITH edge definition>
UNION ALL
<IS_BEST_FRIENDS_WITH edge definition>
)
FROM
GRAPH MyTemporaryGraph
(u1:User)-[:IS_FRIENDS_OR_BEST_FRIENDS_WITH]->(u2:User)
SELECT *;
The text was updated successfully, but these errors were encountered:
Currently, we only support edge patterns with a single label. Again, it would be nice to support more complex edge patterns in queries. For now, users have to simulate multi-label edges by using composition in the edge definition body (given in the workaround below):
must be written as:
The text was updated successfully, but these errors were encountered: