Re: [ojb-users] Transactions and the object cache

[Jiri L. <jir...@ho...>]

Hi Thomas,

> A commited object must be
>removed from all caches in an OJB cluster so that other transaction
>(possibly running in different JVMs on different physical machines) only
>"see" valid data, that is data read in from the DB.

Does this apply to all read objects or just to the objects that are
modified during a transaction? Just make sure...

Jiri.

On Fri, 17 May 2002 12:32:42 +0200, you wrote:

>Hi Paul,
>
>
> > Hi,
> >
> > This may be a naive question and feel free to point me to 'the =
manual',
> > but I don't understand why the ODMG API flushes the object cache =
during
> > a commit.
>
>
>Questions related to caching are never 'naive' ;-)
>The cache is flashed for tx isolation reasons. A commited object must be
>removed from all caches in an OJB cluster so that other transaction
>(possibly running in different JVMs on different physical machines) only
>"see" valid data, that is data read in from the DB.
>
>hth,
>
>Thomas
>
>
> >
> > Thanks in advance,
> >
> > Paul.
> > Ascension Software Limited
> > http://www.ascensionsoftware.com
> > Tel: 01225 484494
> > [Logo]
> >
> > [Home]
> >
> >   w w w . a s c e n s i o n s o f t w a r e . c o m
> >
>
>
>
>
>_______________________________________________________________
>
>Have big pipes? SourceForge.net is looking for download mirrors. We =
supply
>the hardware. You get the recognition. Email Us: =
ban...@so...
>_______________________________________________
>Objectbridge-users mailing list
>Obj...@li...
>https://lists.sourceforge.net/lists/listinfo/objectbridge-users