Re: BUG #1564: special Character OleDB

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: "Steinhaus, Harald" <harald(dot)steinhaus(at)steinhaus(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1564: special Character OleDB
Date: 2005-03-27 16:23:45
Message-ID: 20050327162345.GB16169@dcc.uchile.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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[(at)]dcc(dot)uchile(dot)cl>)
"Always assume the user will do much worse than the stupidest thing
you can imagine." (Julien PUYDT)

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Magnus Hagander 2005-03-27 18:13:11 Re: BUG #1560: Service does not start
Previous Message John Hansen 2005-03-27 10:12:44 Re: BUG #1557: UPPER() and LOWER() do not return the right characters