On Jul 22, 2004, at 2:07 AM, Henri Tremblay wrote:
I don't know if I made myself clear.
I can provide a test case if needed (and continue the discussion in the
forum which is probably a more appropriate place I think).
You didn't. I guess you have to rethink what "not null" means again. It
means a
I think).
Sorry to have made you jump a little,
Henri
- Original Message -
From: "Christian Bauer" <[EMAIL PROTECTED]>
To: "Henri Tremblay" <[EMAIL PROTECTED]>
Cc: "hibernate-devel" <[EMAIL PROTECTED]>
Sent: Thursday, July 22, 2004 12:07 A
On Jul 21, 2004, at 10:42 PM, Henri Tremblay wrote:
Does this remove the hibernate limitation on nullable foreign keys?
(that
foreign keys of collections need to be nullable even if there is a
cascade
all-delete-orphan). If yes, great! If no, still great! (but I'll be
back on
this issue).
What?
Gavin King" <[EMAIL PROTECTED]>
To: "hibernate-devel" <[EMAIL PROTECTED]>
Sent: Wednesday, July 21, 2004 6:32 AM
Subject: [Hibernate] support for ON CASCADE DELETE
> I've implemented support for ON DELETE CASCADE foreign key
> definitions for parent/child associati
> >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
ng in onDelete() via
the session maybe.
Cheers,
Joe
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Gavin
> King
> Sent: Wednesday, 21 July 2004 2:32 PM
> To: hibernate-devel
> Subject: [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
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
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
