On Mar 17, 2010, at 11:28 PM, Igor Stasenko wrote:
the above is an example when object, recorded as an immutable one, then mutated outside a DB transaction. So db can't capture the attempt to modify it. What GemStone doing to handle this?
Actually, GemStone traps object modification at the byte-code level in the VM so does not rely on immutability to be informed of a modification.
James