db-jdo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christiaan des Bouvrie" <c.des.Bouv...@CostEngineering.eu>
Subject Re: refresh()
Date Tue, 01 May 2007 16:06:40 GMT
Hello  Craig,

Thanks for the reply. We do not actually always refreshibecause of the
OptimisticVerificationException, but sometimes we want to make sure the
user is seeing the latest data.

Also, the datastore cache is not shared between clients, since we have a
rich-client application. So imagine the following scenario (not sure if
we have the same scenario in mind, since I cant really explain the need
for flush()):

-          Client A views an object, and loads it in his datastore
cache;

-          Client B views and modifies the same object. His datastore
cache gets updated and also the datastore. 

-          Client A now wants to see the latest version, but the stale
version is still in his datastore cache since it is not shared with
client B. How to get the latest version from the datastore?

 

Kind regard,

Christiaan 

 

 


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message