durusmail: durus-users: changes in the first client not available in the second client
changes in the first client not available in the second client
2004-07-26
2004-07-26
changes in the first client not available in the second client
Neil Schemenauer
2004-07-26
On Mon, Jul 26, 2004 at 03:11:58PM +0200, Ludovico Magnocavallo wrote:
> Running the Quick Demo as suggested in the README, I notice that changes
> in the first client are not available in the second client:

You need to call commit() or abort() in the second client in order
to see the new data.  This behavior is necessary to provide data
consistency.  Between transaction boundaries clients must see a
consistent view of the data.  This necessarily means that they may
be seeing out of date data.

This will be part of the new FAQ that I'm writing. :-)

  Neil

reply