Hibernate version: 3.2.0.ga

If I define a relation when an instance of the POJO where is defined this relation is deleted, that produces a attempt to delete the target of the relation, which is the "parent" of the current POJO, that is a nonsense.
In this case, like that the "on delete cascade" of Oracle, the expected behaviour would rather be that deleting the target of the relation produces the destruction of all the instances of entities which have a foreign key of this target.
If I want to have this behaviour, I must define as much relations in a POJO as this POJO has foireign keys
That can be very heavy, and a lot less flexible that to define this rule on each foreign key (as Oracle does).

I had posted this message on JRA forum, but the answer was "it's a user hibernate question"...

Feel free to implement that and come back crying because your performances suck :-)

Which difference between :
- defining an annotation in an object on a foreign key, which would indicate that the object must be deleted il the object referenced by the f.k. is deleted
- defining a relation OneToMany in the object referenced by the f.k., and indicate on this "CascadeType.REMOVE" ?

The work in the database is the same, no ?

Try it.