My Oracle Support Banner

Merging Entity with BasicCollection Causes Duplicates (Doc ID 1186944.1)

Last updated on SEPTEMBER 10, 2014

Applies to:

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


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


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.