Provide support to increase developer productivity in Java when using Neo4j. Uses familiar Spring concepts such as a template classes for core API usage and lightweight repository style data access.
Saving a Node N that has a relationship to a parent P which in turn has a relationship to a child C causes the relationship between P and C to be updated, even though the relationship between N and P is set to not cascade updates through cascadeUpdates=false.
This means it is impossible to save a node without loading the complete node graph. The weird thing is that the child nodes don't need any populated properties (except the ID), as the cascading update correctly ignores those but not their relationships.
The expected behaviour would be that the relationships of the child nodes also get ignored, when the cascading updates are turned off.
Saving a Node
Nthat has a relationship to a parentPwhich in turn has a relationship to a childCcauses the relationship betweenPandCto be updated, even though the relationship betweenNandPis set to not cascade updates throughcascadeUpdates=false. This means it is impossible to save a node without loading the complete node graph. The weird thing is that the child nodes don't need any populated properties (except the ID), as the cascading update correctly ignores those but not their relationships.The expected behaviour would be that the relationships of the child nodes also get ignored, when the cascading updates are turned off.
I created a minimal example here.