[Hsqldb-developers] Global Statement Compilation in HSQLDB

[Daniel W. <wal...@tc...>]

Hi Devs,

I have a question I couldn't find an answer for online or by investigating
the HSQLDB code myself.

Is there a reason currently in the implementation that the Stateless aspect
of a Prepared Statement when compiled isn't stored in a global
non-connection level cache ?

I have a use case where connections are created and destroyed regularly and
each connection calls 100+ prepared statement creation and executions
during its lifecycle, in a test case that encompasses many other factors I
increased performances by creating a naive low level cache of the compiled
statement to be used each time a new PreparedStatement with a matching sql
string was created.

This had a massive benefit to performance because the statements being
compiled are quite complex.

Is this a feature that hasn't been implemented on purpose ? Or just an open
gap ?

Thanks,
Daniel Walsh
Software Dev