Fred Toussi

Thanks for reporting. I suspect the issue with SqlTool is due to a setting in the SqlTool jar which looks for the HSQLDB jar where it expects it to be, therefore using the 2.7.4 jar. Juse copy the SqlTool jar alongside the Release Candidate jar and specify the RC jar path in the Java command.

HSQLDB version 2.7.5 will be released soon. A release candidate jar is available at https://sourceforge.net/projects/hsqldb/files/release_candidate/ Please try this jar with your applications and report any issues.

HSQLDB version 2.7.5 will be released soon. A release candidate jar is available at https://sourceforge.net/projects/hsqldb/files/release_candidate/ Please try this jar with your applications and report any issues.

Release Candidate jar for version 2.7.5

core code updates - new version 2.7.5

MVCC deadlock

No effect setting hsqldb.cache_size & hsqldb.cache_rows in JDBC connection

Works fine with current SVN trunk: String path = TestDirectorySettings.fileBase +"test17"; TestUtil.deleteDatabase(path); String url = "jdbc:hsqldb:file:" + path; Properties props = new Properties(); props.setProperty("hsqldb.cache_file_scale", "128"); props.setProperty("hsqldb.cache_size", "128000"); props.setProperty("hsqldb.cache_rows", "100000"); Connection conn = DriverManager.getConnection(url, props); The test17.script file contains: SET FILES CACHE SIZE 128000 SET FILES CACHE ROWS 100000...