We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For example, the syntax:
MATCH p=(n1 {type: "compilation_unit"})-[]->(n2 {type: "class_declaration"})-[*2]->(n3 {type: "method_declaration"})-->(n4 {text: "Main", type:"identifier"}) RETURN p
The return type for a path from neo4j has start, end, segments, and notably includes nodes or edge that would be traversed by the edge * operator.
start, end, segments
*
I can still work around it, but I would very much like to have access to variable-length paths!
The text was updated successfully, but these errors were encountered:
Hey @robobenklein! Thanks for the comment, and yes this sounds like a great feature addition! Adding to our backlog :)
Sorry, something went wrong.
Add path groups (#37)
31001b7
* Add path groups #26, #35 * Remove unnecessary enumerate * Update CHANGELOG and bump version in setup.py
@j6k4m8 - I believe this can be closed as fixed with #37?
Yes confirmed! Thank you @davidmezzetti !!
No branches or pull requests
For example, the syntax:
The return type for a path from neo4j has
start, end, segments
, and notably includes nodes or edge that would be traversed by the edge*
operator.I can still work around it, but I would very much like to have access to variable-length paths!
The text was updated successfully, but these errors were encountered: