Ryan Rupp

This was changed/fixed in 3.13.21 (edit - 3.13.16, see linked commit) to ignore calls to `setReadOnly` (and just debug log that it's not supported). See https://github.com/snowflakedb/snowflake-jdbc/pull/885 and https://github.com/snowflakedb/snowflake-jdbc/commit/ed2f855a83ccae3f0609ae16004852af29e4e552

Looks like a fork added this although I didn't test it - https://github.com/andrewmacheret/sqlines/commit/ba512aea20a691e71594835bd2926db3c27045e9

I didn't get a chance to step through this yet but I suspect it's because when referencing a column it can't determine that the column is a date field so...

#2709 looks like it should be fixed in 4.8.4 (which the reporter is using). I'm running into this too and was thinking an upgrade to pull in #2709 would resolve...

My issue seemed tied to multi-line handling so I logged https://github.com/spotbugs/spotbugs/issues/3186 with some example test cases. However, this one also seems similar/maybe the same fix or at least the same...

Note in this use case because the mapping is BIT for boolean values, Spring JDBC Template for setting arguments on a PreparedStatement ends up falling back to `setObject` [here](https://github.com/spring-projects/spring-framework/blob/main/spring-jdbc/src/main/java/org/springframework/jdbc/core/StatementCreatorUtils.java#L460) instead...