suppose I have two table
create table A (
id integer primary key
);
create table B (
id integer primary key,
idA integer not null,
constraint FK_B_TO_A foreign key (idA) references A
(id) on delete cascade
);
Here suppose A to B is a one-to-many association and
I did not ask the hibernate to do the cascade in the
mapping file since I do it in the database by
specifying "on delete cascade"; I think it will be
effecient to let the database to do the cascading
deletion. (Am I right here?).
If I call Session.delete(A), the Session will issue
these two queries:
1. update B set idA = null where idA =?
2. delete from A where id = ?
Apparently hibernate wants to dissociate B from A
before it issues the deletion.
How can I turn this off?
Or any alternative solution?
I am trying to convince my CTO to use hibernate in a
project. However I promise a demo to him sometime
today. Any help is really appreciated.
jason
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
