Hi,
I will check if it is possible to call the function less often. If that's
possible, then no cache would be needed.
Regards,
Thomas
On Fri, Oct 18, 2013 at 2:06 PM, Thomas Mueller
thomas.tom.muel...@gmail.com wrote:
Hi,
I'm sorry but I will revert the change. I will soon try to
On 2013-10-17 18:10, christoff.schm...@finaris.de wrote:
In my project we use H2 table functions to read data from other
databases. I found out that H2 calls our table functions more often
than expected,
which can lead to serious performance problems if the execution of the
SQL from the
Hi,
I'm sorry but I will revert the change. I will soon try to release a new
version so such a change is a bit dangerous. Also I wonder whether it is
really better (faster) to have a cache in the database engine. Do we have a
benchmark? Possibly the equality test (Arrays.deepEquals) might not
Hi,
In my project we use H2 table functions to read data from other databases.
I found out that H2 calls our table functions more often than expected,
which can lead to serious performance problems if the execution of the SQL
from the other database is quite expensive.
The sample code below
