Re: Doubts about encoding, using the database across different OS/encoding

2023-10-17 Thread Rick Hillegas
Character data is always stored and retrieved with UTF8 encoding. If you 
move your database from a Windows to a Linux platform, the character 
encoding will remain UTF8 and everything should work. This assumes that 
you are using character-based methods 
(java.sql.PreparedStatement.setString()/setClob()) to store data and 
character-based methods (java.sql.ResultSet.getString()/getClob()) to 
retrieve it.


Hope this helps,
-Rick

On 10/17/23 10:18 AM, fed wrote:

Hi,

I have some doubts about encoding, I am not an expert about encodings so I
prefer to ask.

Let's say I create and use the database on a Windows pc (so encoding is
like Windows-1252 but not UTF-8, and the application is running with
default OS encoding), I store some text data in tables etc. then I move and
use the database on a linux pc that has encoding UTF-8 and the application
will still run with default OS encoding.

Can this cause problems with text data?
Can the data stored when I was using the database on Windows read wrong on
the Linux system (and vice versa if I move the db again) ?

Thanks for the help
- fed





Doubts about encoding, using the database across different OS/encoding

2023-10-17 Thread fed
Hi,

I have some doubts about encoding, I am not an expert about encodings so I
prefer to ask.

Let's say I create and use the database on a Windows pc (so encoding is
like Windows-1252 but not UTF-8, and the application is running with
default OS encoding), I store some text data in tables etc. then I move and
use the database on a linux pc that has encoding UTF-8 and the application
will still run with default OS encoding.

Can this cause problems with text data?
Can the data stored when I was using the database on Windows read wrong on
the Linux system (and vice versa if I move the db again) ?

Thanks for the help
- fed