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
With Neo4j you can return a collection of nodes, and to support that in cq would require either an ArrayCypherNode type, or use of the ArrayCypherValue type by modifying the CypherValue type so that it can contain a Node. There's already a CypherNode type in the constants for CypherValue, so I think the latter is possible without breaking the existing API. I think the former is a cleaner solution though. Thoughts?
The text was updated successfully, but these errors were encountered:
shiftyp
changed the title
Support a ArrayCypherNode type
Support an ArrayCypherNode type
Dec 5, 2015
I'm ok with either solution (or actually, could do both). I sort of stopped short of creating all the different possibilities of things that cypher can generate, because I realized you can do maps of arrays or arrays of arrays in cypher fairly easily. Even in one liners:
So my philosophy will be: if you need it, I will merge a PR that supports it. It's unfortunate we can't handle these more generically, but that's just one of the things about go.
With Neo4j you can return a collection of nodes, and to support that in cq would require either an
ArrayCypherNode
type, or use of theArrayCypherValue
type by modifying theCypherValue
type so that it can contain aNode
. There's already aCypherNode
type in the constants forCypherValue
, so I think the latter is possible without breaking the existing API. I think the former is a cleaner solution though. Thoughts?The text was updated successfully, but these errors were encountered: