Branch: refs/heads/6.2 Home: https://github.com/hibernate/hibernate-orm Commit: 64c04e24e4b4fe5e127948b8db8180b3368bcc29 https://github.com/hibernate/hibernate-orm/commit/64c04e24e4b4fe5e127948b... Author: Maximilian Zellhofer <max.zellhofer(a)gmail.com&gt; Date: 2023-05-08 (Mon, 08 May 2023) Changed paths: M hibernate-core/src/main/java/org/hibernate/persister/collection/BasicCollectionPersister.java Log Message: ----------- HHH-15393: fix for what looks like a copy & paste error In the changes added to BasicCollectionPersister during HHH-15393, it looks as if generateUpdateRowOperation has maybe been copy-pasted from generateInsertRowOperation (which is perfectly fine), but when the custom sql update row operation is generated, the mutation details for the insert case rather than the ones for the update case are fetched. In case that this assumption is correct, there are some more in buildCustomSqlUpdateRowOperation, where getDeleteDetails() is used instead of getUpdateDetails().