Hi,
I've got a legacy application here using a Neo4j 1.0 (sic!) datastore.
This is now to be upgraded. I understood from the docs that setting
allow_store_upgrade=true and then starting up and shutting down the DB
with each in-between Neo4j release should be a way to go. So the steps are:
1.0 -
Hi,
Am Donnerstag, den 04.08.2011, 14:20 -0700 schrieb noppanit:
Hi,
I'm not sure if I'm missing something here, I'm using Grails with Grails
dependencies to resolve any dependencies. This is my BuildConfig.groovy file
grails.project.dependency.resolution = {
// inherit Grails'
At least we're two now.
I've got also trouble upgrading some code from 1.4M05 to 1.4. It seems
that neo4j-kernel-1.4.jar does not get downloaded to ~/.ivy2/cache.
Regards,
Stefan
Am Dienstag, den 12.07.2011, 13:27 +0300 schrieb Dima Gutzeit:
Is it only me or the artifacts of 1.4 from maven
Are you using the Grails Neo4j plugin or do you just use Neo4j natively
from a Grails app? How did you configure the graph db?
Since you're using WEB-INF/resources/db/neostore as path for neo4j, are
you sure the user running the jvm has write permissions?
Regards,
Stefan
Am Samstag, den
How do you instantiate the GraphDatabase? Via resources.groovy? If so,
make sure to set a destroyMethod.
graphDatabaseService(EmbeddedGraphDatabase, 'my/path') { bean -
bean.destroyMethod = shutdown
}
Next thing to check if Grails reloading causes the error. You might
Hi,
today I released an update of the Grails Neo4j plugin
(http://www.grails.org/plugin/neo4j). The main changes are:
* compatibility with Grails 1.3.x. Be aware, Grails 1.3 - 1.3.3 are
suffering from http://jira.codehaus.org/browse/GRAILS-6427, so either
use Grails 1.2.x, or be brave and use a
Depending on the timeframe I could proably contribute a (sub)chapter
regarding Grails Neo4j
Regards,
Stefan
Am 06.05.2010 10:41, schrieb Peter Neubauer:
Hi Kshipra,
would be awesome to write a book. Mostly, our problem is time. Is there
anyone on the list wanting to contribute or take a stab
Hi,
today I released a minor update of the Grails Neo4j plugin. The changes are:
* performance improvement by no longer calling map constructor in
createInstanceForNode
* fixed transaction handling by replacing interceptor with a “real”
servlet filter
* support for primitve arrays as properties
Hi,
having an event mechanism in Neo4j is definitly a good idea. Just two
quick thoughts on that:
* consider integration into Spring's event stuff:
http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/beans.html#context-functionality-events
* using the proactive
Hi,
I've just released version 0.2 of the Grails Neo4j plugin. The new
version provides:
* domain classes managed by Neo4j can now co-existing with
traditional domain classes
* Upgrade to Neo4j 1.0
* added a seperate controller to inspect the Neo4j node space
* support for the
Hi,
one short question regarding IndexService. What happens if a Node with
indexed properties is deleted via node.delete()? Are the index entries
automatically removed or is the application responsible for this.
A short test showed up, that the node is not found any more using
Hi,
it looks like Node.delete() does not behave as defined in the API docs:
quote
Deletes this node if it has no relationships attached to it. If delete()
is invoked on a node with relationships, an unchecked exception will be
raised. Invoking any methods on this node after delete() has returned
Hi Matt,
see http://bit.ly/7P6yaf, thats a groovy implementation of such a filter
being part of the Grails Neo4j plugin. Should be a piece of cake to
transform this code to Java. There are no dependencies to Grails, it's
completely based on Spring stuff.
In addition to
Hi,
I've just released the initial 0.1 version of the Neo4j Grails plugin.
This plugins provides an alternative persistence layer to Grails: all
domain instances are stored in the Neo4j object space.
There's still a long to go to make this 100% GORM compatible, but basic
things are working,
14 matches
Mail list logo
