> Well, yes, but... I'm not sure it's a correct thing to do. I mean not > ideologically correct. Byte sequence can represent invalid Unicode string > and the usually the behavior of the lamguage/framework/enviroment in such > cases may be hard to predict.
In fact, in Java, the behaviour is predictable. Without further configuration, a java.lang.String is expected to contain UTF-8. So indeed, errors may arise like that. jOOQ could be extended to retrieve both the byte[] and the column encoding from MySQL, in order to correctly fetch a CHAR BINARY type, which could then, again be correctly fetched from the String. I'll think about that in a future release: https://sourceforge.net/apps/trac/jooq/ticket/652 Right now it won't be a priority, though Cheers Lukas
