Mark
Mark
Thanks for the review - have addressed the comments
Thanks for reporting! This issue has to do with prepared statement plan caching which does not work correctly with DuckLake currently. I'm guessing that JDBC uses prepared statements internally. This...
There's an upstream fix for this now here - https://github.com/duckdb/duckdb/pull/17702
This is fixed in the dev version, the fix will land in v1.3.1
This should be fixed now
I may have solved the LinuxRelease failure in https://github.com/duckdb/duckdb/pull/20073 - we will see if it pops up after that
Thanks! Looks great