I think it's normal for JBoss to continue to issue queries for the pks,
after which it uses the associated cache data.
Why do you think that? The commit option A says that the cache is always in
synch with the DB. Consequently, it should first try to find the entity in
cache. If it is in
On Wednesday, December 11, 2002, at 08:30 PM, Sacha Labourey wrote:
I think it's normal for JBoss to continue to issue queries for the
pks,
after which it uses the associated cache data.
Why do you think that? The commit option A says that the cache is
always in
synch with the DB.
findByPrimaryKey is the one finder that can be handled directly by the
cached, all other finders has to go to database to get a list of pks.
/L
onsdagen den 11 december 2002 kl 11.52 skrev Stephen Coy:
On Wednesday, December 11, 2002, at 08:30 PM, Sacha Labourey wrote:
I think it's normal
Because as Dain already stated, JBoss does not have an in memory query
engine (actually, I think he said it when the same question was asked
in the Persistence CMP forum). It uses the database to work out what
entities to return in a finder (by returning just the pks), and then
uses the
On Wednesday, December 11, 2002, at 03:30 AM, Sacha Labourey wrote:
I think it's normal for JBoss to continue to issue queries for the
pks,
after which it uses the associated cache data.
Why do you think that? The commit option A says that the cache is
always in
synch with the DB.
Now that I look closer, it does look like it is just loading PKs.
Thanks for helping me see that.
-H
From: Stephen Coy [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Date: Tue, 10 Dec 2002 14:34:15 +1100
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] EJB Commit Option A Cache Question
I have an application that uses CMP Entities in Commit Option A. I am
testing it on JBoss 3.2 beta 2.
The app uses session facades and servlet+JSP to display the data.
I have a JSP page that displays a list of hotels. It includes a servlet that
calls a SLSB to do a findAll() on the Hotel entity.
Hi,
Are the queries that you are seeing just loading primary keys, or are
there other columns present as well?
I think it's normal for JBoss to continue to issue queries for the pks,
after which it uses the associated cache data.
If you are seeing other columns in the queries, then you may be
