Thank you, that does force a write of the database files. And the database seems to stay at the same size so the space is indeed reused. Unfortunately the shutdown subsequently triggers failures on connections that are pulled out of my connection pool for the same database. So I need to shutdown the database and purge all connections for this database from the pool to force a database write. Is there any other way to force the writes without shutting down the database?
I have tried that approach using hsqldb.files_space=2 in the connection string. In that case the error does not occur but a very strange thing happens: during the first test-run a database.data file is created and the data is written to it. The second run succesfully retrieves the data, drops, recreates and repopulates the tables. But after that any subsequent run does no longer see the tables created during the previous runs. After the first run the database.data file is never touched again. It...
BTW: I am using 2.4.1 for this now.
Well, it has taken some time but I have managed to implement this. But now I get: Access is denied in statement [SET TABLE "PUBLIC"."DEMO" NEW SPACE] Any ideas?
I understand that NEW SPACE is a per table setting. I was just hoping for something...
I understand that NEW SPACE is a per table setting. I was just hoping for something...
Hello Fred. Thanks for the response. I have never compiled HyperSQL from source but...
Some closer observation revealed that database size does not grow linearly but exponentially...