Eclipse Community Forums: EclipseLink » EclipseLink-7251: is mapped to a primary key column in the database. Updates are not allowed.

Home » Eclipse Projects » EclipseLink » EclipseLink-7251: is mapped to a primary key column in the database. Updates are not allowed.

Show: Today's Messages :: Show Polls :: Message Navigator

EclipseLink-7251: is mapped to a primary key column in the database. Updates are not allowed. [message #990874]

Fri, 14 December 2012 15:39

Igor B

Messages: 9
Registered: July 2012

Junior Member

Hi,

I have the following Entity:

public class A extends Base {

private EmbClass abcEmbClass;

@Embedded
@AttributeOverrides({ @AttributeOverride(name = "EmbClass", column = @Column(name = "ABCEMBCLASS")) })
public EmbClass getAbcEmbClass() {
return abcEmbClass;
}
}

@MappedSuperclass
public abstract class Base {

private EmbClass embClass;

@EmbeddedId
public EmbClass getEmbClass () {
if (embClass== null) {
embClass= new EmbClass();
}
return embClass;
}
}

So far so good.

Now the implementation does the following:

public A update(AVo aVo) {
A _a = aEm.find(A.class, aVo.getEmbClass());
_a.setAbcEmbClass(aVo.getAbcEmbClass)
aEm.merge(_a);
return _a;
}

The primary key EmbClass is not changed at all, only a foreign key, so why happens the following error:

Exception Description: The attribute [embClass] of class [EmbClass ] is mapped to a primary key column in the database. Updates are not allowed.
[java] at org.eclipse.persistence.exceptions.ValidationException.primaryKeyUpdateDisallowed(ValidationException.java:2458)
[java] at org.eclipse.persistence.mappings.foundation.AbstractDirectMapping.writeFromObjectIntoRowWithChangeRecord(AbstractDirectMapping.java:1214)

How can I fix this problem?

best regards,

Igor

Report message to a moderator

Re: EclipseLink-7251: is mapped to a primary key column in the database. Updates are not allowed. [message #991502 is a reply to message #990874]

Wed, 19 December 2012 14:51

Chris Delahunt

Messages: 1389
Registered: July 2009

Senior Member

Try copying the EmbClass instance instead of reusing instances as embeddable objects are not meant to be shared. Each reference should have its own independent instance to be used to track changes.

Report message to a moderator

Previous Topic:	Weird problem of persist in another transaction
Next Topic:	entity extensions in a secondary table

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 20:21:53 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter