On Wednesday, December 11, 2002, at 03:30 AM, Sacha Labourey wrote:
Actually, JBoss always checks the cache to see if the bean is present for all commit options. In A it works as described before. In B, some beans may be in the cache but invalid and only the valid ones are used (i.e. ones in the current transaction), and in C only beans in the current transaction are in the cache.Why do you think that? The commit option A says that the cache is always inI think it's normal for JBoss to continue to issue queries for the pks,
after which it uses the associated cache data.
synch with the DB. Consequently, it should first try to find the entity in
cache. If it is in cache, there is no need to issue a db query. If it is not
in cache, then a query is necessary.
-dain
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
