Re: 22021: invalid byte sequence for encoding \"UNICODE\": - Mailing list pgsql-bugs

From Andreas Pflug
Subject Re: 22021: invalid byte sequence for encoding \"UNICODE\":
Date
Msg-id 418286FD.9080204@pse-consulting.de
Whole thread Raw
In response to 22021: invalid byte sequence for encoding \"UNICODE\": 0xe16d61"  ("Lucas Sultanum" <lucas.sultanum@gcf.com.br>)
List pgsql-bugs
Lucas Sultanum wrote:
>
> I am not sure if this is a bug or I am doing something wrong. When I
> execute the following command (*insert into a_cadclias values
> ('6542','65465','amaro','ámaro')*)  on pgAdmin III Query it works pretty
> well, but when I try to do the same through a C# App connecting to the
> database through an ODBC driver I get the following error:
>
> *"ERROR: 22021: invalid byte sequence for encoding \"UNICODE\": 0xe16d61"*

Sounds as if you're not using the correct client encoding; your app is
probably non-unicode, but you're using client encoding Unicode.

Regards,
Andreas

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Dropdb, Win32 Problem
Next
From: Stephan Szabo
Date:
Subject: Re: Insertion Deferrable