From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Emmanuel Guiton <emmanuel(dot)guiton(at)intrinsec(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: JDBC driver, client_encoding and a SQL_ASCII database in production |
Date: | 2010-03-10 12:17:02 |
Message-ID: | 4B978DBE.8090506@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Emmanuel Guiton | 2010-03-10 13:32:25 | Re: JDBC driver, client_encoding and a SQL_ASCII database in production |
Previous Message | Emmanuel Guiton | 2010-03-10 11:18:23 | JDBC driver, client_encoding and a SQL_ASCII database in production |