Review of Cascade.REMOVE and Cascade.PERSIST #98

hceylan opened this Issue Nov 18, 2012 · 1 comment

2 participants

Batoo Software member

Having resolved the issue #97, I now have come to rethink the cascade behaviour.

Since the spec requires immediate calling of callbacks for PrePersist and PreRemove, it may be required to treat additions to the collections as persist() calls and removals with orphan removal set as remove() calls.

We need to investigate what the specification says.

@schueffi since you are expert in scanning the spec, would you like to give your input on that?

Batoo Software member

reviewed persist and remove and its working.

@asimarslan asimarslan closed this Mar 9, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment