Menu

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

current-release
open
nobody
None
5
2026-01-21
2026-01-19
YPP
No

Dear all,

we are defining below properties in the JDBC connection but only 2 of them seem to be working:
- hsqldb.cache_file_scale set to 128
- hsqldb.cache_size set to 131072000 (128 MB)
- hsqldb.cache_rows (set to 100000)

We're using HyperSQL (2.7.3) in embedded mode.

After initiating the first connection, the .script file generated contains:
- SET FILES SCALE 128
- SET FILES CACHE SIZE 10000
- SET FILES CACHE ROWS 50000

Would there be a bug? Or the 2 properties hsqldb.cache_size and hsqldb.cache_rows cannot be set via the JDBC connection?

Thank you in advance and best regards.

1 Attachments

Discussion

  • Fred Toussi

    Fred Toussi - 2026-01-20

    The cache size prop must be in kilobytes, in this case 128000.

     
  • YPP

    YPP - 2026-01-21

    so that property will really only be considered only with certain values?

    couldn't a rounding be done in the code to consider all values?

     
  • YPP

    YPP - 2026-01-21

    Just tested with 128000 that doesn't work either, the .script file still contains

    SET FILES CACHE SIZE 10000.

    Maybe that setting isn't supported in JDBC connections?

     
  • Fred Toussi

    Fred Toussi - 2026-01-21

    Most properties are applied to a new database at the time of creation. Make sure the database files do not exist.

     
  • YPP

    YPP - 2026-01-21

    thanks for your quick inputs.

    Files don't exist.

    Could there be issues with e.g. connection pools?

     
  • Fred Toussi

    Fred Toussi - 2026-01-21

    Please test without connection pool. I will check this before the next release and if there is a regression it will be fixed.

     

Log in to post a comment.