Merging Entity with BasicCollection Causes Duplicates (Doc ID 1186944.1)

Last updated on SEPTEMBER 10, 2014

Applies to:

Oracle TopLink - Version 11.1.1.1.0 to 11.1.1.3.0 [Release Oracle11g]
Information in this document applies to any platform.

Symptoms

When upgrading from TopLink 11.1.1.1.0 (EclipseLink 1.0.1) to TopLink 11.1.1.3.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 11.1.1.1.0 (EclipseLink 1.0.1) to TopLink 11.1.1.3.0 (EclipseLink 2.0.2) .



Cause

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