Filtering and paginating on @cypherNode and @cypherRelationship

[a-type]

Connecting directives need more control over how the data is queried.

Research:

• What clauses are allowed in list projections?

Implement:

• Matching based on arbitrary user defined parameters
• ORDER BY / SKIP / LIMIT

Questions:

• Is there any point to these directives, or could @cypher just be expanded to work in nested scenarios?

[a-type]

Research results: only WHERE is allowed in list projections (opencypher/openCypher#202).

Ordering, skipping, limiting will all be blocked on better sub-query support (opencypher/openCypher#217), but if that gets added to the spec, the library will get a major feature boost!

A fake pagination could be introduced by slicing up the list comprehension, but it would not be lazy, and without ordering it doesn't feel very useful. List ordering currently unsupported (opencypher/openCypher#190).

Alternate approach to achieving nested paginated fields: manually combine subqueries by chaining WITH blocks then pull them back into a final map projection (yikes!)... might end up doing it. Query perf might be worse due to eager operations, but I think that's going to be unavoidable if the schema uses pagination at each field level anyways.

[a-type]

Next steps:

• Add WHERE clause support to @cypherNode and @cypherRelationship (Add where arg to @cypherNode and @cypherRelationship #4)
• Prototype allowing nested @cypher directives using WITH chaining

[SpaghettiFactory]

This is marked as blocked. What is needed in order to implement this?

[a-type]

Hi @SpaghettiFactory ! I admit this project isn't really on my radar anymore, but here's how I remember it -

Basically, without first-class subqueries, Cypher can't really support nested pagination. I don't quite remember the specifics, but I believe this library uses field projections to accomplish nested structures, and field projections don't allow for standard pagination constructs to be used (or at least, not to the extend that they could enable cursor-based pagination).

This issue was related, and is still open - opencypher/openCypher#217

Limitations with Cypher for this use case in particular was, as I recall, why I ended up shopping around for different graph databases to use behind GraphQL. I had a bit of success with ArangoDB, which does support subqueries in its query language.