Hello,

I have a problem with a bidirectional relationship.

I use cascade "all-delete-orphan" to persist changes in sub-objects when modifying object parent.

1. If I insert a new parent, the sub-objects are correctly inserted in DB

2. If I delete a parent, the sub-objects are correctly deleted from DB

3. On the opposite, when I try to update an object parent, Hibernate always try to insert the list of
sub-objects instead of updating them (even if they already existed in DB)
It is like it always interprets that the sub-objects are new.


In the beginning I thought that the problem could be related with the bidirectional relationship (below mapping), but
as it works for the inserts and deletions, now I am thinking that is not the point.

Parent:



Child:



I really would appreciate any light.
Thank you.

I suppose that you are updating the list be overwriting it entirely, right?



That might cause your issue.

Instead, you need to:

- remove the child entities that are no longer needed
- add new child entities when necessary
- update the content of the child entities that are to remain in the DB

When you add/remove child entities, you have to synchronize both ends of the association as explained in this article.

Hello again,

Thank you for your answer but I think that I am doing the correct process:



As you can see, I only modify the 1st item of the sub-objects collection.

How is possible Hibernate interprets the sub-items are new if they arrive to the method to persist with their IDs?

Thank you.

Can you add the SQL queries that Hibernate executes?

Hello,

1 - First of all, the query (simplified as it is quite big) to retrieve the object (parent and children) to be modified:



(*) I've just paid attention in one thing: Why it queries twice the same column: descriptio1_.BODY_DESC_UID?


2 - The instructions to update the DB:



You can see it tries to execute an "insert" instead of an update, and in that moment the exception by constraint violated is thrown as two field that must be different for each row are repeated:

Maybe you're using an old version of Hibernate, or maybe there's something else down the stack that you're doing that's causing this issue.

Try running this example from our documentation and you'll see that it's working as expected.

Try debugging it and see what's causing the EntityInsertAction to be triggered. It's difficult to say without seeing the code.

Yes, I know it should work, as I did it for another tables.

I do not understand how it tries to insert if the id field is populated in the sub-entities.

Hello,

I stil have not be able to solve the problem and this is breaking our planning.

Any idea?


Thank you very much

I have no idea. Send us a replicating test case that demonstrates this behavior since I haven't ever seen it.

Hello,

The problem was caused by this property I had mapped:




Thank you for your help.