Re: BUG #1564: special Character OleDB - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #1564: special Character OleDB
Date
Msg-id 20050327162345.GB16169@dcc.uchile.cl
Whole thread Raw
In response to BUG #1564: special Character OleDB  ("Steinhaus, Harald" <harald.steinhaus@steinhaus.de>)
List pgsql-bugs
On Fri, Mar 25, 2005 at 10:43:08AM +0000, Steinhaus, Harald wrote:

> using charset SQL_ASCII German special characters are correctly shown in
> pgAdminIII.
> In a WindowsForms Application using PgOleDb-1.0.0.19 these characters are
> shown as ? and removing the following character.

If you are using SQL_ASCII, you should not insert non-7-bit-ascii data.
If you do, you are responsible for whatever may happen with character
conversion; which means, it will work on some cases, but will fail on a
lot of others.

You should really declare the correct character set at creation time
(which depends on the locale you choose), and issue the correct "SET
client_encoding" command at execution time.

> (Using other charactersets didn't allow use batchimport when the file
> contains special characters

Probably that's because you didn't define the correct client_encoding.
See the thread at

http://archives.postgresql.org/pgsql-general/2005-03/msg00892.php

--
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
"Always assume the user will do much worse than the stupidest thing
you can imagine."                                (Julien PUYDT)

pgsql-bugs by date:

Previous
From: "John Hansen"
Date:
Subject: Re: BUG #1557: UPPER() and LOWER() do not return the right characters
Next
From: "Magnus Hagander"
Date:
Subject: Re: BUG #1560: Service does not start