Re: String Encoding Conversion Problem

On Tue, Jun 24, 2008 at 11:31:16AM -0500, Ryan Wells wrote:
> Subject: [GENERAL] String Encoding Conversion Problem
> 
> We've got a .NET application that's trying to move data from an old MySQL database to a shiny new Postgres db, but we keep getting this error: 
> invalid byte sequence for encoding "UTF8": 0xf66a6e69
>  
> The MySQL table is using "latin1 -- cp1252 West European" and the Postgres server is using UTF8.

You'll have to use any of the documented methods of telling
PostgreSQL that the client is loading data in the "cp1252"
encoding.

Doing so revolves around setting the client_encoding
parameter at either of the transaction, database, client-,
or server-OS level, whatever is more appropriate.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346