On Fri, 2002-03-08 at 14:50, David Jencks wrote: > How did you deal with the problem of: > > A changes object 1 on server s1 and commits > B changes cached object 1 on server s2 and commits > notification arrives from s1 to s2 that cached object 1 is invalid >
In our case, since we were using 'row versioning' when B tried to commit, it would fail since the database was updated. That's why versioning is used in some cases. Without versioning, then if the above case happens, its 'last one in wins'. Bad for say bank transactions, eh? ;-) -- Virtually, Ned Wolpert <[EMAIL PROTECTED]> D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45
signature.asc
Description: This is a digitally signed message part
