Shouldn't SaveEventDelegate#preSave take as well a depth parameter to limit the depth visit?

[nithril]

Hello,

org.neo4j.ogm.session.delegates.SaveDelegate#save(T, int) is taking a depth parameter but not SaveEventDelegate#preSave. The visit of the nodes can be pretty extensive. Is it on purpose?

[gerrit_meier · Accepted solution]

The question seems to be incomplete but I just assume that you were asking for the unreachable() processing.

This will only be done for the up until the level the data was loaded initially.
Example with horizon on load:
A->B->C and you load only A->B remove the B from A and you do a save(A, 500) (intentionally high number), it will only process B in the unreachable list because it is the only removed relationship that "changes" (from existence to void).
Example without horizon on load:
A->B->C and you load only A->B->C remove the B from A and you do a save(A, 1), it will still only process B in the unreachable list. Even if you would remove C from B in the same run. So the dangerous this in this situation is that your graph model will diverge from your Java model.

[nithril]

Thank you for your answer. I better understand the needs now.