Dick Hildreth

I was getting the error "exists=true, locked=false, valid=false," on database startup on Linux and I finally decided that, since the owner and group for data was root, hSQLdb could't write out the .lck files. I entered the hSQLdb directory and entered the commands: sudo chgrp [myusername] data sudo chown [myusername] data I don't know whether only one was required, but I was tired of messing with it. It worked! Probably the same applies to Mac and BSD, as well as any flavor of UNIX. I probably wouldn't...

This is not your issue, but I'm hoping that you have some insights. I'm migrating hSQLdb to Server 2019. On Server 2012 R2, I launched hSQLdb as a Windows service using the procrunsrv (Apache Commons Daemon) wrapper. I was able to install the service but, when trying to start the service, I got an error "the data area passed to a system call is too small". Note that, simply running hSQLdb using the (slightly modified) bat files provided works fine. The service install/run bat file is: REM hSQLdb...

Is there, or are there any plans to have, an interface for accessing hSQLdb from JavaScript environments like Node.js, etc?