I've implemented support for ON DELETE CASCADE foreign key
definitions for parent/child associations (ie. for inverse
one-to-many).
You map this like:
set name=children inverse=true cascade=all
key name=PARENT_ID on-delete=cascade/
one-to-many class=Child/
/set
So, when the Parent instance
Max Rydahl Andersen wrote:
Sounds like a nice and performant feature.
By doing this we are now skipping/ignoring the LifeCycle stuff on
these objects, correct ?
Nope, all semantics are preserved. This *only* optimizes away the delete
statements.
And this is also a step in the direction of