Hi all,
I was doing some application profiling today. I found that in our
real-world scenario of loading a database using many different very long
SQL statements, a significant amount of H2's CPU time was being spent in
org.h2.command.Parser.initialise().
Further investigation revealed that by
Hi,
If you use PreparedStatement, and the re-use them, within the same
connection, you should be fine, even without the "query cache".
The cache "query cache" is only for those cases where you use Statement
instead of PreparedStatement, or if you re-create the PreparedStatement
each time. That in
Hi,
Sorry, I originally forgot to update the website. But this should be done
now.
Regards,
Thomas
On Sat, Aug 1, 2015 at 2:35 PM, 이정주 wrote:
> Hi
>
>> Thank you for the new release.
> Website yet seem unchanged
> :)
>>
>>
>
> --
> You received this message because you are subscribed to the G
