BUG #1298: 22021: invalid byte sequence for encoding \"UNICODE\": 0xe16d61" - Mailing list pgsql-bugs

From PostgreSQL Bugs List
Subject BUG #1298: 22021: invalid byte sequence for encoding \"UNICODE\": 0xe16d61"
Date
Msg-id 20041028124949.724625A1195@www.postgresql.com
Whole thread Raw
List pgsql-bugs
The following bug has been logged online:

Bug reference:      1298
Logged by:          Lucas Sultanum

Email address:      lucas.sultanum@gcf.com.br

PostgreSQL version: 8.0 Beta

Operating system:   Windows 2000 server

Description:        22021: invalid byte sequence for encoding \"UNICODE\":
0xe16d61"

Details:

Hello,


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"

I know that it has something to do with the word ámaro because when I take
the letter (á)off and replace it with the letter (a) it works fine.

Bellow goes the table structure:


CREATE TABLE a_cadclias
(
  dba_clias_cliente "numeric"(8) NOT NULL,
  dba_clias_associado "numeric"(8) NOT NULL,
  dba_keyclias_sq "varchar"(8) NOT NULL,
  teste "varchar"(10),
  CONSTRAINT dba_keyclias_sq PRIMARY KEY (dba_keyclias_sq)
)
WITH OIDS;


Att: It is valid to said that I have also tried the Npgsql dll and got the
same error.
Versions tested:
"PostgreSQL 8.0.0beta2 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC)
3.2.3 (mingw special 20030504-1)"

AND

"PostgreSQL 8.0.0beta4 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC)
3.3.1 (mingw special 20030804-1)"



Regards

Lucas Sultanum

pgsql-bugs by date:

Previous
From: "PostgreSQL Bugs List"
Date:
Subject: BUG #1301: pg_restore failed on AMD 64bit machine
Next
From: "PostgreSQL Bugs List"
Date:
Subject: BUG #1299: ordinal 2821 no en contrado en LIBEAY32.DLL