| CDOSetFeatureDelta.getOldValue is always UNSPECIFIED [message #653938] |
Fri, 11 February 2011 23:56  |
 Cameron Bateman
Messages: 3
Registered: February 2011 |
Junior Member |
|
|
When I have an CDOObject commited to a repository, say "foo" and I do something like:
foo.setName("foo");
commitInfo = trans.commit()
foo.setName("bar");
commitInfo2 = trans.commit();
I correctly get a CDOSetFeatureDelta back in commitInfo2 corresponding to "name" being set to "bar". However, I always seem to get the "UNSPECIFIED" object for the oldValue rather than "foo", which is what I would have expected.
Does anyone have any idea why this might be happening?
[Updated on: Fri, 11 February 2011 23:56] Report message to a moderator |
|
|
| Re: CDOSetFeature.getOldValue is always UNSPECIFIED [message #653965 is a reply to message #653938] |
Sat, 12 February 2011 05:37  |
|
Am 12.02.2011 00:56, schrieb Cameron Bateman:
> When I have an CDOObject commited to a repository, say "foo" and I do something like:
>
> foo.setName("foo");
> commitInfo = trans.commit()
> foo.setName("bar");
> commitInfo2 = trans.commit();
>
> I correctly get a CDOSetFeatureDelta back in commitInfo2 corresponding to "name" being set to "bar". However, I always seem to get the "UNSPECIFIED" object for the oldValue rather than "foo", which is what I would have expected.
>
> Does anyone have any idea why this might be happening?
We've never put much effort in remembering *local* oldValues in the CDOFeatureDeltas because they're not transfered to the server or other clients anyway. But you're right in that it looks inconsistent from a CDO API user's point of view. I think we've fixed this in https://bugs.eclipse.org/bugs/show_bug.cgi?id=336729
Cheers
/Eike
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Powered by
FUDForum. Page generated in 0.02910 seconds
] 
Search
Help
Register
Login
Home
