Re: Per field encoding
Well, that's the issue, isn't it?
The specs say the driver will convert from UNICODE to the database char format, but your database is set to use Latin1, and we already know that sending large data in Latin1 doesn't work when the target column actually uses UTF-8.
As I explained before, Connector/J cannot infer the actual charset of the target column so there's no way to know the right encoding to use in each one of the setCharacterStream() calls. The next best alternative is to allow the user to specify the encoding to use in character streams, when it differs from the session encoding -- `clobCharacterEncoding`.
I understand this may not work for you but in the end Connector/J is technically limited by the MySQL protocol and there's no way to work around it.
Subject
Written By
Posted
Re: Per field encoding
May 13, 2024 06:51PM
Sorry, only registered users may post in this forum.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.