Running into an error where the first time a query executes (using the cursored execution mode) it works, but running it again fails because my SQL Server didn't recognize the cached prepared statement handle.
In my use-case, disabling the statement cache would be sufficient - my queries don't run very often. But in general, perhaps having discovery options that can control this cache, or exposing PreparedStatementCache as a type that applications can provide their own implementation of, would be suitable?
As a workaround I am reflectively updating the ConnectionOptions.preparedStatementCache field with my own "NoCache" implementation. But this is obviously not ideal.
I'm using 0.8.5.RELEASE, and running on Java 11. SQL Server version is 2012.
Running into an error where the first time a query executes (using the cursored execution mode) it works, but running it again fails because my SQL Server didn't recognize the cached prepared statement handle.
In my use-case, disabling the statement cache would be sufficient - my queries don't run very often. But in general, perhaps having discovery options that can control this cache, or exposing
PreparedStatementCacheas a type that applications can provide their own implementation of, would be suitable?As a workaround I am reflectively updating the
ConnectionOptions.preparedStatementCachefield with my own "NoCache" implementation. But this is obviously not ideal.I'm using 0.8.5.RELEASE, and running on Java 11. SQL Server version is 2012.