Hi Lukas,
I have a similar issue, and it looks like a JDBC bug:
The 6.0.5 release log claims they've solved the issue, but the problem still applies to normal VARCHAR columns.
I tried converting the table from latin1 to utf8mb4, changing the characterSetResults to latin1, then utf8, but nothing works.
The only thing that works is using ResultSet.getBytes instead of getString:
new String(res.getBytes("columnName"), "UTF-8")
Is there any way I can get JOOQ to use getBytest instead of getString?
Thanks,
Daniel