>
> Can anyone comment on how we can use this library to get all nodes?
> Something like: graphClient.RootNode.OutV("*")?
Is there a method like graphClient.V() ? If so, thats the one.
Marko.
right now the Neo4j REST API doesn't expose all-nodes and all-relationships directly b/c this kind of operation is not suited over the wire as it would result in transferring your whole database content in the RESTful json format (which is quite verbose).
What is your actual use-case?
The node(*) is a new syntax which might not yet be reflected in the Neo4jClient-API.
2. and 3. are for Romiko / Tatham to answer, Tatham is currently in London, he presented Neo4jClient at the Neo4j user group.
Michael
Thanks for checking out the client.
> I've been on the project website and the documentation there is not extensive.
Which parts do you want expanded? We only want to document the .NET layer, not neo4j itself. Cypher support is only brand new, and still in flux, as the doco states.
> 1. How can I get all nodes?
We haven't got support for node(*) yet in our Cypher wrapper. I can add it quickly, but I'm wondering what you need it for? It sounds incredibly inefficient. It'd be like running SELECT * FROM EvveryTableEver in SQL.
> 2. How can I tell the query to return the data in the correct way for serialization?
Our current Cypher implementation is focussed on projections. I'm working in support for basic result sets next. In the meantime, Gremlin is an easier option.
> 3. Is there a better way I could be doing this query? is there a way to do something like var Nodes = client.Get<data.Person>("*")?
You need to start by modelling your graph a bit. Currently you have the assumption that every node is a person, and always will be, and there are no relationships.
If you can explain a little bit about what you want to store, we'll all be able to help you with that.
On a related note, I did a talk in London last night about neo4j for .NET devs. The recording should be online at http://skillsmatter.com/podcast/home/neo4j-dotnet/js-3423 in the next day or so.
-- Tatham
(The library gets expanded out as we need each feature, and the need to query every single node ever just hasn't presented itself to us yet.)
-- Tatham
The video is now up: http://skillsmatter.com/podcast/home/neo4j-dotnet/js-3724