[Neo4j] Problems with neo4j-shell

did not change anything. It seems to me that at least since M03 something in the shell is broken or I am missing something that since then changed in the handling of the shell. Any help on how to resolve this problem would be very much appreciated. Best regards, Sebastian Stober __

Re: [Neo] Strange behavior of LuceneFulltextIndexService

gt; 2009/12/21 Mattias Persson : >>> Ok great, I'll look into this error and see if I can locate that bug. >>> >>> 2009/12/21 Sebastian Stober : >>>> Hello Mattias, >>>> >>>> thank you for your quick reply. The new behavior y

Re: [Neo] Strange behavior of LuceneFulltextIndexService

rry" --> (1), (2) > * o "larry Wachowski" --> (1), (2) // lucene's default operator is OR > * > * The default AND/OR behaviour can be changed by overriding > * {...@link #getDefaultQueryOperator(String, Object)}. > */ > > >

[Neo] Strange behavior of LuceneFulltextIndexService

Hello, I ran into some strange behavior of the LuceneFulltextIndexService in the application I am building. So I put together a junit test based on the example from http://wiki.neo4j.org/content/Indexing_with_IndexService#Wachowski_brothers_example Here's what I found out using 0.9-SNAPSHOT of in

[Neo] LuceneIndexService - update value for key

Hi, I would like to update the value for a key for some node. Currently, the only way I see is to do something like this: index.removeIndex(node, key, oldValue); index.index(node, key, newValue); However, for this I need to know the old value. What if I don't? Is there a way to a) retrieve the v

[Neo] Problem iterating large relationship lists

. Cheers, Sebastian -- Sebastian Stober E-mail: sto...@cs.uni-magdeburg.de University of Magdeburg WWW:http://www.dke-research.de/stober.html FIN ITI - DKE Group Phone: +49-391-67-12728 Universitaetsplatz 2 Fax:+49-391-67-12020 39106 Magdeburg, Germany ___