[Hibernate] Middlegen Hibernate plugin 5 - released.

Hi, I have just released the Middlegen-Hibernate plugin R5. It has significant improvements and fixes. I recommend all Hibernate-plugin users upgrade to this version. Download package from HIbernate SF downloads. The release notes follow. Enjoy, Cheers David. -

Re: [Hibernate] Middlegen Hibernate plugin 5 - released.

Fantastic, great work, David! :-) David Channon wrote: Hi, I have just released the Middlegen-Hibernate plugin R5. It has significant improvements and fixes. I recommend all Hibernate-plugin users upgrade to this version. Download package from HIbernate SF downloads. The release notes f

[Hibernate] support for ON CASCADE DELETE

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: So, when the Parent instance is deleted, Hibernate does not need to perform n+1 deletes; instead, we leave that to the database to take ca

Re: [Hibernate] support for ON CASCADE DELETE

Hello Gavin, Wednesday, July 21, 2004, 6:32:11 AM, you wrote: > 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: > > > > > So, when the Parent instance is deleted, Hibernate

Re: [Hibernate] support for ON CASCADE DELETE

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 supp

RE: [Hibernate] support for ON CASCADE DELETE

I like it, added flexibility; I haven't thought this through much, but could the parent object, if it implemented the Lifecycle interface, tell that its a cascaded delete via onDelete or some other way? Maybe an onDeleteCascade() method in case its helpful to trap, or some way of telling in onDelet

RE: [Hibernate] support for ON CASCADE DELETE

> >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. Perfect :) Sorry for the other post, just sent as