Re: JDBC driver, client_encoding and a SQL_ASCII database in production
От | Oliver Jowett |
---|---|
Тема | Re: JDBC driver, client_encoding and a SQL_ASCII database in production |
Дата | |
Msg-id | 4B978DBE.8090506@opencloud.com обсуждение исходный текст |
Ответ на | JDBC driver, client_encoding and a SQL_ASCII database in production (Emmanuel Guiton <emmanuel.guiton@intrinsec.com>) |
Ответы |
Re: JDBC driver, client_encoding and a SQL_ASCII database in production
|
Список | 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 по дате отправления: