ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Vissers <Jan.Viss...@cumquat.nl>
Subject Re: why does SqlMap ibatis is slower that JdbcDaoTemplate
Date Thu, 06 Oct 2005 22:20:47 GMT
Thanks for sharing, I was always under the impression that inline 
parameters didn't mean hard parses. I'm quite aware of the fact that 
this might hurt Oracle.

Checking...

Sven Boden wrote:

>Simple... the SQL code executed by the JDBC example and the iBATIS
>version is not the same. The JDBC examples use parameter markers and
>proper arguments, while the iBATIS version in the original mail uses
>inline parameters, the #value# (which means that the SQL generated
>will contain hardcoded parameters)... By the way iBATIS can also use
>parameters markers.
>
>Oracle performance suffers very badly when using hardcoded arguments.
>I could make my own example but have a look e.g. at Tom Kyte's site
>http://asktom.oracle.com and search for "hard parsing"... you will get
>a complete explanation why hardcoding is bad.
>
>Personally I've seen in Oracle examples of executing SQL in a loop
>with different arguments where with proper parameters the code would
>take 2 seconds, and with harcoded arguments the "same" SQL took 2
>minutes.
>
>So if the database is Oracle a more proper comparison would be to
>hardcode the arguments in the JDBC example, or use parameter markers
>in iBATIS.
>
>Regards,
>Sven
>
>
>On Thu, 06 Oct 2005 23:45:41 +0200, you wrote:
>
>  
>
>>Hi Sven,
>>
>>Like to hear from you, how you came to that conclusion.
>>
>>-J
>>
>>    
>>
>
>
>
>  
>

-- 
Cumquat Information Technology
De Dreef 19
3706 BR Zeist
T +31 (0)30 - 6940490
F +31 (0)10 - 6940499
http://www.cumquat.nl

Jan.Vissers@cumquat.nl
M +31 6 51 169 556



Mime
View raw message