Hi again; Bumping a database to an incompatible format is something one usually doesonly in a major release, for good reasons. On the issue of migrating, I asked Claude and the answer is: I found a specific, documented limitation: HSQLDB dropped support for reading the 1.8.x on-disk file format starting in 2.5.1. A GitHub commit bumping a project from 2.3.1→2.6.1 notes it explicitly: "Support for HSQLDB 1.8 file format was dropped in HSQLDB 2.5.1; before this change, you could use HSQLDB versions up to 2.5.0; after this change, you can use HSQLDB versions 2.0.0 and higher." ...
My suggestion: let's bump the database to version 2.5.0 initially. The patch shouldn't change a lot (it was made for 2.0), but someone else has to test it. Pedro. ps. sqlite as an alternative sounds interesting.
