Nigel, thanks for pointing out server side vs client side considerations.
On 18 Jun 2014, at 21:22, Nigel Small ni...@nigelsmall.com wrote:
Hi Gareth
All of py2neo's features use the Neo4j REST interface, both for Cypher and
for its other functions. The main difference concerns where the
Hi Nigel,
Out of curiosity - it appears that your py2neo works quite seamlessly with
Cypher by using the append / execute / commit steps. (I actually ended up
loading in my data using py2neo's Cypher module.) I would appreciate your
take on py2neo's Cypher implementation vs. py2neo's
Hi Gareth
All of py2neo's features use the Neo4j REST interface, both for Cypher and
for its other functions. The main difference concerns where the application
logic exists: on the server or on the client.
With Cypher, all the logic is encapsulated within the language itself and
will be
I am preparing a Neo4j database on which I would like to do some network
analysis. It is a representation of a weakly connected and static physical
system, and will have in the region of 50 million nodes where, lets say,
about 50 nodes will connect to a parent node, which in turn is linked
Hi Gareth
As you identify, there are certainly some differences in terms of
performance and feature set that you get when working with Neo4j under
different programming languages. Depending on your background, constraints
and integration needs, you could consider a hybrid approach whereby you
