Hi All,

I am having a serious problem that I just can't solve. I have a parent object with multiple children. I have updated the classnames in this example to protect our project but the idea is the same. Here are the mappings.

Parent mapping contains:


Child mapping contains:


In my code I execute the following:
getHibernateTemplate().delete( parent );

In this example the parent object is an instance of a parent object loaded by hibernate.

When the code is executed I get an error stating that a Child row cannot be update because PARENT_ID cant be set to null. It seams as if Hibernate is trying to detach the parent from the child by setting the reference to null instead of deleting the child entirely. If this is true, isnt this a bug in hibernate?

Thanks in advance,
Martyn

Have you tried with cascade="delete"? I think the delete-orphan option is useful only when you are removing child elements from the parent set. Eg. parent.getChildrenSet().remove(child).

I tried your solution but unfortuntly it doesn't work. I still get the following error:

ORA-01407: cannot update ("DBUSER"."CHILD"."PARENT_ID") to NULL

I checked my own (almost identical) mapping again. It turns out that I have inverse="true" also on the <set>:



And indeed, if I remove the inverse="true" attribute I get a similar error (I am using MySQL):



So, the solution would be to have: cascade="delete" inverse="true"

Thanks, I tried that but now I'm getting another error:

ORA-02292: integrity constraint (DBUSER.MULTIPLE_CHILD_R1) violated - child record found

I examined the database and MULTIPLE_CHILD_R1 is the foreigen key name for the child to parent relation. So PARENT_ID column has a foreign key that points to the unique id of the parent.

The mapping child 2 parent mapping looks like this:


Martyn

Hi all,

I'm also having the same problem with cascades on merges and deletes with a table having a many to one, one to many relationship. Did any of you happen to figure out why hibernate NULLs out fields on the entity that are marked as "nullable=false"? This problem has been bothering me for quite some time now.

Thanks,
Wade