JDBC: Connection to HSQLDB database does not permit update

I was able to migrate an existing LO Base embedded database to a standalone HSQLDB instance with server (per http://hsqldb.org/doc/2.0/guide/guide.pdf, Appendix C) on Windows 10. I can access the standalone database using JDBC just fine, and query all the tables/views using username “SA”. Note server tracing is enabled, so console reports all submitted commands to confirm remote client transactions. However, the returned data seems to be read-only as LO will not permit any updates. I have verified the database properties have readonly=false. I suspect the issue may be that JDBC connections are read-only by default. Anyone know if this is true, and how to change it such that JDBC connections are updateable?

Note before migration, the same database when embedded permitted updates just fine.
Relevant property file content below.

LO version:
JRE version: 1.8.0_152

=== server.properties ===

=== database.properties ===
#HSQL Database Engine
#Thu Jan 11 19:18:38 CST 2018


Can’t seem to duplicate with v1.8.0 or v2.3.2. What JDBC driver class name are you using? Just curious as to why you are not using a newer HSQLDB version? The guide you point to is v2.4!

Hey, thanks for the response. I am using the HSQLDB release bundled with the LO distribution. The JAR archive is found at “C:\Program Files\LibreOffice 5\program\classes\hsqldb.jar”, which was added to the JRE classpath.
I will try a newer version of HSQLDB to see if the issue is resolved using it.

@Spun69 Please REMOVE the classpath from Options->Advanced as this will cause major problems in using new versions of HSQLDB server. Want to avoid this setting for HSQL. Other DB’s are OK such as MySQL. Checking on some other potential issues also which may affect you.

@Ratslinger After upgrading the database to use HQSL 2.4, the original issue seems to have gone away. I can now update tables via JDBC connection. Thanks for the suggestion. This ticket can be closed.
BTW I did set the JRE classpath within LO for my most recent testing (before I saw your response). I am curious how the newer JAR file will be found within LO if there is no explicit path given…I would think it would fallback to using the old one bundled with LO version. Please clarify.

As stated, the setting of classpath will cause problems with embedded files. It will make them inoperable after the first open. To avoid this, remove the HSQL classpath. Change the internal setting of the .odb for the classpath with a macro found in the LO docs (here) - Appendix on page 26.

I finally found the relevant doc (BaseHandbook v5 Appendix pdf), and implemented the specified macro. Retested and no issues found. Seems like I am good to go at this point. Thanks again for the prompt help.

Upgrading the HSQLDB installed version to 2.4, and migrating database to new version, seems to have corrected the issue. Can update database via JDBC (using newer hsqldb.jar) from within LO.

@Spun69 Just to be clear, are you all set? Everything working? NO class path set? If all OK, please respond & then close question.

Issue is now resolved WITHOUT using LO classpath.