Обсуждение: String Encoding Conversion Problem

Поиск
Список
Период
Сортировка

String Encoding Conversion Problem

От
"Ryan Wells"
Дата:
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.  We're narrowed the problem down to the special characters in what appears to be some Swedish text (hopefully they'll make the transition to email):
 
Onormal höjning av kroppstemperaturen, oftast till följd av något sjukdomsförlopp. (MeSH Swedish)
 
This may actually be more of a .NET string conversion issue, but I wanted to check and make sure there's not some obvious database angle we're missing.  Does anyone have any experience with or insight into these sorts of string compatibility issues?
 
Thanks!
Ryan

Ryan Wells
Application Developer, SOAPware, Inc.
www.SOAPware.com
1-800-455-7627
 

Re: String Encoding Conversion Problem

От
Karsten Hilbert
Дата:
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
keepgetting 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