Re: Per field encoding

[Tom Eugelink]

Thank you. That confirms that the JDBC does not support the feature of MySQL that it allows for different encodings per table.

I cannot expect a generic ORM framework to support features that the own JDBC driver does not, e.g. by using different connections for each table.

The "patch" for the problem, BTW, is to not use the ORM's LOB annotation. That way it won't use the setCharacterStream but setString. I am confused why setString handles the encoding, and why whatever makes that work isn't present in setCharacterStream.