Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.0 branch
-
None
-
None
-
Tested on Windows XP client with 2003 Server
Description
When an object is deleted in a context on an ROP client and the context is committed, the object is deleted in the database but still seems to be in the context.
An example is having object A with a To array of B Objects.
One of the B objects is deleted. The context is then committed. The object is removed from the database.
Then, when looking at the size of the ObjectA.toBArray the size is still the same and object is still there.
My work around has been;
context.deleteObject(B) ;
ObjectA.getToBArray.remove(B);