
This is how one would convert an embedded HSQL 1.8 into a stand-alone HSQL manually with a minimum of scripting:
1) Extract the database folder
2) Rename all the database files (script, properties, data etc) to DB_NAME.script, DB_NAME.properties, DB_NAME.data etc.
3) menu:Edit>Database>Connection... Type JDBC and enter a valid URL such as jdbc:hsqldb:file:///path/DB_NAME
4) Enter the driver class org.hsqldb.jdbcDriver
Now this will not work because no driver can be found.
5a) Drop support for embedded HSQL and add a class path to some hsqldb.jar to the office configuration.
OR
5b) Keep support for embedded HSQL and add a class path to some hsqldb.jar stored in the document. This requires a one line macro because the GUI does not have any such input box. I stumbled upon property JavaDriverClassPath while browsing the API on connection settings.
1) Extract the database folder
Can someone confirm this malfunction, at least in Linux ... because under Windows everything seems to work (loading two drivers of different version is possible...)
Users browsing this forum: No registered users and 5 guests