Merging Entity with BasicCollection Causes Duplicates
Last updated on SEPTEMBER 10, 2014
Applies to:Oracle TopLink - Version 220.127.116.11.0 to 18.104.22.168.0 [Release Oracle11g]
Information in this document applies to any platform.
When upgrading from TopLink 22.214.171.124.0 (EclipseLink 1.0.1) to TopLink 126.96.36.199.0 (EclipseLink2.0.2). a problem is encountered.
When merging an entity that has BasicCollection mapping, the existing entries of the BasicCollection is inserted again causing duplicate rows or unique key constraint violation (if the primary key is the id of the CollectionTable). This behavior changed from TopLink 188.8.131.52.0 (EclipseLink 1.0.1) to TopLink 184.108.40.206.0 (EclipseLink 2.0.2) .
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms