Steven Schlansker

@LittleMikeDev, that's a slightly different problem. I've improved the error messaging to not be misleading about the class that is missing the annotation: https://github.com/jdbi/jdbi/pull/1590/files#diff-75b1c04d402bd8924262c7fececfcdb1L166

@TorRanfelt, I dug a bit more into this and it is not obvious what to do to fix it. It looks like the Kotlin compiler is not emitting a bridge...

As a workaround, Jdbi could emulate the needed bridge method. The code needed probably ends up being small but very tricky to write. I hope Kotlin will at least evaluate...

It looks like this was a compromise to maintain Java 6 compatibility: 6 did not support bridge methods in interfaces, so Kotlin does not emit them. That sounds mighty silly...

I appreciate your frustration @sskrla, this issue has been open for a very long time. I do not understand why Kotlin has not fixed it yet: this is a serious...

Hi @skradel , thanks for reporting this issue. I wrote a small test case: ```java @Test public void testDoubleBatchInsert() { h.useTransaction(tx -> { final Runnable insertBatch = () -> tx.prepareBatch("INSERT...

What version of Postgres do you use when you observe this impressive speedup? there was some important work on planning prepared statements around the Postgres 9 days, IIRC. The gist...

Does the problem persist if you install the `PostgresPlugin`? It's not installed automatically by the rule, so you can test without it when need be.

I agree, it's an odd behavior. JDBC drivers have different requirements around `null` handling - in particular, Postgres is much pickier about declared types on null values. We can keep...

Ah, I am not so sure we can fix this as stated originally. In particular: ``` batch.bind("uuid", (UUID)null); ``` This will lose all information about the `UUID` type -- nulls...