iBatis will not return the results faster than DB.Do a showplan on your querry, or have a senior developer that knows SQL look at the querry.It looks like somone went out of the way to force a tablescan and sort of 5 million records..V
If you're using SimpleDataSource, you can force close all connections
by using SqlMapClient.getDataSource(), cast it to
SimpleDataSource, and call .forceCloseAll().
Cheers,
ClintonOn 9/2/05, Paul Glezen <[EMAIL PROTECTED]> wrote:
Because that only tells me "what". It doesn't tell me "why". So I
Because that only tells me "what". It doesn't tell me "why". So I do trace the JDBC driver. But when I have an iBatis commit in my code and see no commit in the driver, I'd like to see why. When the JDBC driver says autocommit was set to false, and I see commits despite not calling commit, I'd
Why not just switch on you db vendor logging facility i find this far more
useful.
Steve
From: Paul Glezen [mailto:[EMAIL PROTECTED]
Sent: Fri 02/09/2005 16:37
To: user-java@ibatis.apache.org
Subject: Re: Ibatis and Junit tests
This is precisely the kind of
This is precisely the kind of thing that would be apparent if the iBatis logging were a bit more verbose. I asked about this earlier on the list and didn't see much of a response. We shouldnt' have to dig into iBatis source code to know about important events like driving close, commit, etc.
-
How much data are you getting back with your query? 10 rows? 100 rows?
1000 rows? 1 rows?
If you are getting back more than you *need* for the report, you
should look at doing all the data processing with a stored procedure
instead of in Java code. This will improve performance in several ways
IMO iBatis does call connection.close() after commit/rollback, but if
you are using any kind of connection pooling physical connections will
obviously survive.
I tryed to locate where forceCloseAll method (that closes all pooled
connections) is called for SimpleDataSource, but could not... Maybe
Thank you for your suggestion.
I tried it but I get the same problem while trying to drop the db after the end
transaction in tearDown().
By the way, I don't understand how it could work. My understanding is that a
connection can be reused for several transactions.
What do I miss?
--- Jim Shea
Jean-Francois,
Thanks for the reply and agreed your comments.
We have also identified the SQL query optimization makes the big difference in the performance,so we modifed the quries as much as possible.
Moreover,
1. we have not implemented the cache model till now,so we are planning to include
Hi,
From what I can see, this is not in iBATIS
that you should look for better performance but in your SQL select statements.
It is always a bad idea, in a where
clause, to use a function on an indexed column like in:
SUBSTRING(NewLog_T.date,1,4) = #syukeiYear_#
AND
This way,
10 matches
Mail list logo
