Hi,
one of our customers is facing the following problem while using our
product, which uses an embedded H2 database (v. 1.3.173).
The query looks like this:
SELECT INITIAL_FIXED_VOL, FIXED_YIELD_4AVG, FIXED_ORIGMAT_4AVG,
INITIAL_FLOAT_VOL, FLOAT_YIELD_4AVG, FLOAT_ORIGMAT_4AVG
FROM
I have no idea what the underlying problem is.
But if you could create a standalone test case for it I could probably track it
down.
In the meantime you could probably work around it by bumping up your cache size.
Append something like this to your URL
;CACHE_SIZE=1024
where the size is in
