Re: Per field encoding
Posted by: Tom Eugelink
Date: May 06, 2024 03:58AM

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?

Options: ReplyQuote


Subject
Written By
Posted
May 02, 2024 05:39AM
May 03, 2024 05:02AM
May 03, 2024 06:46AM
Re: Per field encoding
May 06, 2024 03:58AM
May 06, 2024 04:23PM
May 10, 2024 07:17AM
May 10, 2024 10:58AM
May 10, 2024 11:03AM
May 13, 2024 06:51PM
May 13, 2024 11:56PM


This forum is currently read only. You can not log in or make any changes. This is a temporary situation.

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.