I'm sure the corruption was not there using 1.3.161 because its just an
empty scheme I created once back then (i can send it if it helps).
Whatever happens in that file later on, happens by a more recent h2.jar
(1.3.168 in this report).
I completely understand there's nothing you can do
I assume that that fact (that the h2 version with which i created the
schema = 1.3.161) is not relevant for the problem experienced in 1.3.168
which is still a problem in 1.3.168?
It is true that i have created a schema once using an older h2, and kept
that db file as a file to start of in my
Hi,
Well, the problem is, if the database was created with an old version, then
the corruption might have been there already when you switched to a new
version. Corruption problems are very hard to analyze, because there is no
log file that tells us which change in the database file was created
Here's another example of ArrayIndexOutOfBoundsException at
org.h2.index.PageDataLeaf.getRowAt: this happened on 1.3.168. The most
recent fix i found in changelog about this kind of error was 1.3.166, so
probably there's still something wrong since then, or have there been fixes
related to
On 2013-08-13 10:05, Dieter Cailliau wrote:
Here's another example of ArrayIndexOutOfBoundsException at
org.h2.index.PageDataLeaf.getRowAt: this happened on 1.3.168. The most
recent fix i found in changelog about this kind of error was 1.3.166,
so probably there's still something wrong
