Storing particular paths as named variables (perpetually)

[opteflon]

is there a way to 'store' specific paths as variables / references?

e.g.

(a)-[R]->(b)-[S]->(z) is stored as path1 (rl example 'LA to New York via Atlanta')
(a)-[T]->(c)-[U]->(w)-[V]->(z) is stored as path2 (rl example 'LA to New York via Dallas and Miami')

This example (just like my use case) the same 'origin' / 'destination' can have multiple 'valid' paths, but it's vital to detail the exact path that particular use-case takes.
Having these alternative paths stored against variable names for easy referencing querying etc.
Even if stored as a json doc or anything - or can be stored directly into the database somehow?
(am struggling with google / searching due to difficult / overlapping terminology here)
Many thanks

[Joel]

Cypher supports storing specific paths in a variable like this

MATCH p=(a)-[R]->(b)-[S]->(z)
RETURN p

The path(s) returned by the search are stored in the variable p.

You mentioned 'specific path' but I suspect by your example that you might be looking for a way to store the 'path search pattern'? Like an alias I guess? Where are you running this query? In Neo4j Desktop? Saving cypher is easy to do in application code, the cypher is just a string.

[ameyasoft]

Here is one solution that I provided in an earlier post. Check this:

How to save the result of a query (sub graph) in cypher Neo4j Graph Platform

Here is a solution that I used, Collected the ids of nodes, created a node and added the ids list as a property. Step: 1 match(n)-[r]->(m) where not m.name in ['JANSSEN','PFIZER\BIONTECH','ANOFI PASTEUR','Hospital','Recovered'] and not n.name in ['JANSSEN','PFIZER\BIONTECH','ANOFI PASTEUR','Hospital','Recovered'] with collect(distinct id(n)) as n1, collect(distinct id(m)) as m1 with apoc.coll.union(n1, m1) as res1 with apoc.coll.sort(res1) as final merge (a:SubGraph {name: "xyz", ids: final}…