Re: Per field encoding
I understand the fact that encoding settings are done at the connection level. And you should really not want different encodings in a database, but it is what we have, no use in blaming the past.
What I am confused about is that setString handles it this deviating encoding correctly, while setCharacterStream does not. How can that be?
Subject
Written By
Posted
Re: Per field encoding
May 06, 2024 03:58AM
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.