Hibernate version: 3.2

A question about cascading . . .

Let's say I have a table "A" which maps to class "A" and
a table "B" which maps to class "B"

Their relationship is one-to-many, that is A can have many B's.

Table and class B contains idA, a foreign key to A.

Now let's say I delete a record from A and I want the corresponding idA in B to be set to null. How should I set the cascade option here?

<bag name="BList">
<key column="idA"/>
<one-to-many class="B"/>
</bag>

Thanks

Eric

Admittedly Im new to hibernate myself but my guess is, you don't have
to cascade anything. If you modify A (remove the B from the collection) and then flush your session / commit the transaction then I would assume that
B is updated to be removed from A.

Arne

It depends on how you design your model. If the relationship is bidirectional, which means that B can only have one parent of type A, then maybe the B object should be deleted from the DB if you delete its parent A.

Or maybe not, which imply that B may not have a parent (in other words, the parent property of B may be null). In this case, you must explicitly detach the B object from its parent A before removing it.

I am not sure just removing the parent will set the parent property of B to null.

Thanks for the replies!

arne was correct. I acheive the desired outcome by not declaring a cascade and not declaring inverse to be true.


badgerduke