On 2 June 2010 16:21, Mattias Persson wrote:
> I don't think the python bindings (or any other binding) has caught up
> to the new traversal framework. Uniqueness is all about when to visit
> a node and when not to. If the uniqueness would be NODE_GLOBAL a node
> wouldn't be visited more than onc
2010/6/2 Javier de la Rosa :
> Thank you for your clarification.
>
> On 2 June 2010 13:31, Mattias Persson wrote:
>
>> "return filter": {
>> "language": "javascript",
>> "body": "position.node().getProperty( 'name' ).equals( 'Javier' )"
>> }
>>
>
> Will we see "language": "python" in the nea
I don't think the python bindings (or any other binding) has caught up
to the new traversal framework. Uniqueness is all about when to visit
a node and when not to. If the uniqueness would be NODE_GLOBAL a node
wouldn't be visited more than once in a traversal. NODE_PATH means
that a node won't be
And one more question, what's the meaning of "uniqueness": "node path"
parameter? What values does it support? Which is the equivalent en neo4j.py?
--
Javier de la Rosa
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinf
Thank you for your clarification.
On 2 June 2010 13:31, Mattias Persson wrote:
> "return filter": {
>"language": "javascript",
>"body": "position.node().getProperty( 'name' ).equals( 'Javier' )"
> }
>
Will we see "language": "python" in the near future?
--
Javier de la Rosa
_
2010/6/2 Javier de la Rosa :
> I'm developing the support to traversals for Python REST Client. The
> underlying idea for me is to mantain the compatibility with neo4j.py (a
> really hard issue), but the traversals made me to think about some
> questions:
> 1. How can I implement support to isStopN
I'm developing the support to traversals for Python REST Client. The
underlying idea for me is to mantain the compatibility with neo4j.py (a
really hard issue), but the traversals made me to think about some
questions:
1. How can I implement support to isStopNode or isReturnable in REST
Service? I
7 matches
Mail list logo
