Yes, the same with me. It complains that the database is opened by
another process, but it is obviously not.
I also encountered another compatibility issue between neo 1.1-1.2: neo
1.2 tries to read a wrong value from index.db, so I had to delete
index.db, let my program rebuild it, then it
2010/11/12 Balazs E. Pataki pat...@dsd.sztaki.hu
Yes, the same with me. It complains that the database is opened by
another process, but it is obviously not.
Maybe Anders Nawroth can look into it...
I also encountered another compatibility issue between neo 1.1-1.2: neo
1.2 tries to read
I also encountered another compatibility issue between neo 1.1-1.2: neo
1.2 tries to read a wrong value from index.db, so I had to delete
index.db, let my program rebuild it, then it runs OK. I used the
laboratory version of the Lucene indexer with neo 1.1.
Oh, good to know. The storage
Chris,
you are right, this is wrong in the documentation. I updated it to be
correct, should be deployed in some minutes via the build system.
Thanks for spotting it!
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn
Hi!
Neoclipse 0.41 uses Neo4j 1.0 and has no way of shutting down the
database instance.
The trunk version of Neoclipse uses a recent Neo4j version and it's
possible to shut down the database.
Instructions for how to build the plugin from source are found here:
Peter,
Most excellent! Sounds like a perfect Christmas / New Years gift... ;-)
Thanks! Chris
Message: 2
Date: Thu, 11 Nov 2010 13:24:08 +0100
From: Peter Neubauer peter.neuba...@neotechnology.com
Subject: Re: [Neo4j] neo4j.py issue reading index
To: Neo4j user discussions user@lists.neo4j.org
Hi,
I thought many of you might be interested in using JUNG over Neo4j.
http://github.com/tinkerpop/blueprints/wiki/JUNG-Graph-Implementation
This support has been in Blueprints for many months now, I just never
documented it.
Take care,
Marko.
http://markorodriguez.com
7 matches
Mail list logo