Sorry if I'm inundating the list w/ too many emails. =D I've been loving Cypher -- way more user-friendly and powerful than the REST API's traverse method -- but I'm finding even Cypher isn't optimized for queries where I really want to fetch a *subgraph*, not tabular data.
I can give plenty of scenarios if that helps (I've even drawn diagrams!), but the theme in my queries is repeatedly that I need to understand the relationships between nodes in our graph, which means I want subgraphs. I understand that the traverse method in the REST API gives you the option of returning nodes, relationships, or paths. I'd like to propose a new return type: subgraph (or graph). Here's what I'm envisioning: the JSON contains an adjacency matrix of nodes and relationships -- referenced entirely by URLs -- and an additional map from URL to data (properties) for each referenced node and relationship. Here's an example format: https://gist.github.com/1171908 I'd *love* to be able to query and fetch subgraphs from the graph like this. That would be so awesome. I'd love thoughts and feedback. Cheers, Aseem _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
