First off, thanks for py2neo. I think i found a bug that prevents from
using javascript filters when traversing over rest:
http://py2neo.org/docs/api/py2neo.neo4j-pysrc.html#TraversalDescription.filter
Instead of body, key is named name. Since you're on vacation i've
taken justice of sending you
Hi Krzysztof
Yes, certainly looks like it's a bug, however I'm convinced this has changed
from the original REST docs on which I based this code. Can't find a copy
though and since your fix looks to apply to both 1.4 and 1.5 then
consider it merged!
Thanks for your help :-)
Nige
*Nigel Small*
No problem, on the other hand the name parameter is still valid,
since there are two named filters: all and all_but_start_node, and
whatever filters someone may add themselves.
I also have one issue with Node class, i really like the way original
JPype bindings work - i.e. i can use
So that we can support both, I've made some further changes to the
TraversalDescription class. I have replaced prune and filter with:
builtin_prune_evaluator(self, name)
prune_evaluator(self, language, body)
builtin_return_filter(self, name)
return_filter(self, language, body)
This does break
No need to, i submitted a pull request with that change. I will also
submit my proposed index syntax changes. I'm no good at git, so i may
or may not screw this up.
As far as changes you wrote about, i think we should move it to one
method, and rely on arguments supplied by user to know which
Hi Krzysztof
Having looked at your Pull Request, I can see that your syntax certainly
provides a easy and readable way to create relationships to nodes. However,
I have a couple of reservations:
1. This essentially uses a get operation to carry out a write behind
the scenes. I would generally
Hi Michael
Completely agree on named parameters - I'd like to support both named and
positional - both have advantages.
I also like the idea of the {foo} syntax as consistency with Cypher is what
I have tried to provide all along here. I actually don't believe that it
will be confusing with JSON
...noticed my last example didn't render properly, Should have been:
(dad) {name:Nigel}
(son1) {name:Joshua}
(son2) {name:Stephen}
(dad)-[:FATHER_OF]-(son*)
(son*) {lastname,Small)
Hope that works this time!
*
*
*Nigel Small*
Phone: +44 7814 638 246
Blog: http://nigelsmall.name/
GTalk:
Hi there,
I think prototyping a parameter approach to start with would be great!
Nigel, you up for it?
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter
Yep, absolutely. Probably won't get a lot done this week though as I'm on
holiday in México at the moment and don't have much in the way of dev kit,
plus the wireless is a little flaky. That said, I'll start poking it if I
get the time and see how far I get.
So in summary, assuming we are going
Nigel,
On Thu, Nov 10, 2011 at 11:01 PM, Nigel Small ni...@nigelsmall.name wrote:
We could possibly create some form of syntax which would designate a this
node, e.g. (@). This could allow a file to reference it's external context,
in this case the node to which we are submitting the subgraph.
Hi Peter
Imagine we are trying to inject a simple graph, such as the following:
(dad) {name:Nigel}
(son1) {name:Joshua}
(son2) {name:Stephen}
(dad)-[:FATHER_OF]-(son1)
(dad)-[:FATHER_OF]-(son2)
Currently, this would be loaded into graphspace without any attachment to
existing structures; a join
Nigel,
Sounds good, although I'd rather have named parameters as well, otherwise
parameter indexes will easily get unwieldy.
I would like to propose to use the same syntax cypher uses for parameters
(that's also the syntax used by the batch-inserter)
aka. {0} and {name}
Thanks Nigel for working hard on Py2neo - it's becoming a very cool binding!
Also, GEOFF for the clean insertion of data is starting to shape up -
I am hoping to get server side support in after the release :) Related
to this is another issue. How are we going to insert subgraphs that
refer to
Hi all
Have just released a small but hopefully significant (performance-wise)
upgrade to py2neo: a rewrite to geoff.py which submits the entire set of
data in a single self-referential batch. Available from GitHub and PyPI.
Cheers
*
*
*Nigel Small*
Phone: +44 7814 638 246
Blog:
15 matches
Mail list logo
