|
Re: double record in history [message #654195 is a reply to message #653675] |
Mon, 14 February 2011 14:48 |
|
Ca you include the mapping code and the SQL generated.
Are you using a ManyToManyMapping with a HistoryPolicy?
The result seems correct though? You set the reference to null and removed it, and it nulled the reference and then recorded it as no long active?
James : Wiki : Book : Blog : Twitter
|
|
|
|
|
|
|
|
|
Re: double record in history [message #654927 is a reply to message #654874] |
Thu, 17 February 2011 16:16 |
|
In general EclipseLink updates objects that will be deleted if they are changed, as the update may be desired by the user and required to resolve constraints.
If you don't want the update, the best solution is to not update your object.
EclipseLink does have an option to performDeletesFirst which you could enable, this will avoid the update, but could lead to deletion constraint issues.
You could also refresh or revert the object before removing it.
In general the update should not cause any issues, so you could just ignore it as well.
James : Wiki : Book : Blog : Twitter
|
|
|
Powered by
FUDForum. Page generated in 0.04200 seconds