Re: JDBC driver, client_encoding and a SQL_ASCII database in production - Mailing list pgsql-jdbc

From Oliver Jowett
Subject Re: JDBC driver, client_encoding and a SQL_ASCII database in production
Date
Msg-id 4B978DBE.8090506@opencloud.com
Whole thread Raw
In response to JDBC driver, client_encoding and a SQL_ASCII database in production  (Emmanuel Guiton <emmanuel.guiton@intrinsec.com>)
Responses Re: JDBC driver, client_encoding and a SQL_ASCII database in production  (Emmanuel Guiton <emmanuel.guiton@intrinsec.com>)
List pgsql-jdbc
Emmanuel Guiton wrote:
> Hello All,
>
> I am using Pentaho Data Integration (PDI) to transform a database in
> production to some other database, correctly structured for my business
> intelligence analysis purpose.
> PDI uses the JDBC driver to perform the transformation. The issue is
> that JDBC only works with UTF-8 as client_encoding while the charset of
> the database in production is SQL_ASCII and was filled with ISO-8859-1
> characters (and is full of characters such as é è ô ...). The only way I
> can get the correct string back is to use client_encoding='LATIN1'.
>
> Changing the character set of the original database is not an option as
> it is in production.
>
> Anyone has a good idea on how could I proceed to get correctly the
> content ?

Take a copy of the production database, change the database encoding to
be LATIN1, and do your conversion from that copy?

-O

pgsql-jdbc by date:

Previous
From: Emmanuel Guiton
Date:
Subject: JDBC driver, client_encoding and a SQL_ASCII database in production
Next
From: Emmanuel Guiton
Date:
Subject: Re: JDBC driver, client_encoding and a SQL_ASCII database in production