Thanks Mattias for the suggestion.
What if we had a method in IndexHitsNode as below.
ListIteratorNode listIterator = IndexHitsNode.getListIterator()
The ListIterator can traverse in both ways as opposed to Iterator which is
forward only.
If that solves the reverse traverse problem for
The implementation in IndexHits doesn't keep previous results in memory,
which is a good thing IMHO. So your suggestion that there should be a
getListIterator on IndexHits makes sense and is really the same solution (at
least how I would choose to implement it) in that it would return a new
Hi all,
I create a new database neodatabse using neo4j python version.
#create new databse
graphdb = neo4j.GraphDatabse(neodatabse)
graphdb.shutdown()
Then re open it in other function and added some nodes and indexes
#open databse
graphdb = neo4j.GraphDatabse(neodatabse)
try:
tx =
Mmh,
let me file an issue, and let's see if it gets picked up in the bindings!
https://trac.neo4j.org/ticket/264
Cheers,
/peter neubauer
VP Product Development, Neo Technology
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn
Ups sorry it's my mistake. actually it was tx.success() instead of tx.finish()
and still everything is save but the indexes.
From: Francois Kassis
Sent: Friday, September 17, 2010 12:20 PM
To: user@lists.neo4j.org
Subject: Saving indexes in neo4j.py
Hi all,
I create a new database
The pattern matcher requires a starting node to start the search from.
If the pattern you are trying to match is find all persons who are
married and live together you could do something like this:
PatternNode person1 = new PatternNode();
PatternNode person2 = new PatternNode();
PatternNode
Hi
Is it not possible to call org.neo4j.graphdb.index.Index#remove when
it's triggered from a beforeCommit event ?
I get the following exception:
(The TxData object contains the removed property
(removedNodeProperties) that I want lucene to remove from it's index
with the remove method.)
I'm not convinced I like the way this works:
POST /node/123/paths {to: http://localhost:/node/456;, algorithm:
shortestPath, max depth: 100}
Isn't the intention to retrieve the shortest path? If so I'd prefer:
GET
Until Neo4j supports operations on distributed graphs, couldn't we assume the
destination
is another node in the same graph and clean that up to:
GET /node/123/paths?to=456algorithm=shortestPathmaxDepth=100
Also, I believe Neo4j only has a stable of reindeer. Would one of them do?
/Andreas
On
2010/9/17 Jim Webber j...@webber.name
I'm not convinced I like the way this works:
POST /node/123/paths {to: http://localhost:/node/456;,
algorithm:
shortestPath, max depth: 100}
Isn't the intention to retrieve the shortest path? If so I'd prefer:
GET
10 matches
Mail list logo