Hi,
I confirm the issue is on my side. I made optimization in MapDB which causes
the
bug (replaced for loop copy with System.arrayCopy)
Thanks for help and sorry for false alarm.
Jan
On Wednesday, May 28, 2014 13:41:24 Thomas Mueller wrote:
Hi,
Yes, it looks like this doesn't affect H2.
2014-06-01 10:16 GMT+02:00 Cecil Westerhof cldwester...@gmail.com:
2014-05-09 15:30 GMT+02:00 Germano Rizzo germano.ri...@gmail.com:
I have a reproducible bug with versions 174 and 176 (at least). A db
created with 1.3.174 (no particular settings) corrupts when just opening
and closing it
Hi,
I could analyze it now. The problem seems to be that creating a temporary
table is not committed, and then the temporary table is deleted in another
session. I have a fix / workaround for that, but so far no test case.
Please tell me if you have a reproducible test case.
Regards,
Thomas
Hi,
Yes, this problem was introduced in version 1.3.176, actually by fixing
another bug. It happens when upgrading a database with a special kind of
foreign key constraint from an older version to 1.3.176. I found the
problem now and have a fix for it. I will need to release a new version; a
Hi,
I finally found and fixed the problem now. This problem will be fixed in
the next release. One workaround is to not upgrade to version 1.3.176 if
the database was created with an earlier version. Another workaround is to
export the database file to a SQL script and re-create it.
Regards,
Great work, Thomas, thank you.
Will I be able to open a database created with 174, and never opened in
176, with the new version?
Thanks again,
Germano
Il giorno lunedì 2 giugno 2014 18:04:13 UTC+2, Thomas Mueller ha scritto:
Hi,
Yes, this problem was introduced in version
Running a recovery, the resulting db file is 5x larger, and still growing.
I just had a bulk load deadlock. I'm not sure how to interrupt these
things, but started with kill -INT, then kill -SEGV, then kill -KILL. After
that the db could not be opened, and would dump a bunch of lines like this
Hi,
Will I be able to open a database created with 174, and never opened in
176, with the new version?
Yes. Even if opened with version 1.3.176 multiple times actually. No data
is lost, the change just prevents the (old) database from being opened.
Regards,
Thomas
--
You received this
