Re: 22021: invalid byte sequence for encoding \"UNICODE\":

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Lucas Sultanum <lucas(dot)sultanum(at)gcf(dot)com(dot)br>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: 22021: invalid byte sequence for encoding \"UNICODE\":
Date: 2004-10-29 18:07:57
Message-ID: 418286FD.9080204@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Stephan Szabo 2004-10-29 18:33:16 Re: Insertion Deferrable
Previous Message Bruce Momjian 2004-10-29 17:44:43 Re: Dropdb, Win32 Problem