Thanks Michael!
~A
On Mon, Oct 13, 2014 at 6:57 PM, Michael Hunger
michael.hun...@neotechnology.com wrote:
The more recent versions use and index for your IN query, so it will
actually use an index or constraint in this case, that fix was added after
2.0.3 though.
On Mon, Oct 13, 2014
Hi Aru
Firstly, as a side note, the issue to which you link highlights a problem
with the deb/rpm packages for some versions of Neo4j. The tarballs are fine
and py2neo is definitely compatible with all versions from 1.8 upwards.
Now to your main question
Neo4j is optimised for efficient
Hi Nigel,
Thanks for your response. It's relieving to hear that this might be related
to the deb package I used to install Neo4j. I will experiment with that
shortly.
I totally get what you're saying with the data modeling bit. In my case we
have already modeled our domain (i.e., these nodes
The more recent versions use and index for your IN query, so it will
actually use an index or constraint in this case, that fix was added after
2.0.3 though.
On Mon, Oct 13, 2014 at 11:33 PM, Aru Sahni arusa...@gmail.com wrote:
Hi,
Disclaimer: I'm using Neo4j 2.0.3. I know that this is far
