From: Markus Bertheau <mbertheau.pg@googlemail.com>
To: Christian Paul B. Cosinas <cpc@cybees.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: PostgreSQL Handling of Special Characters
Date: Mon, 20 Mar 2006 10:09:24 +0600
Message-ID: <684362e10603192009s28a0afe4m@mail.gmail.com> (raw)
In-Reply-To: <001701c64bce$968d59f0$1e21100a@ghwk02002147>
References: <200603200114.k2K1EtF29584@candle.pha.pa.us>
<001701c64bce$968d59f0$1e21100a@ghwk02002147>
2006/3/20, Christian Paul B. Cosinas <cpc@cybees.com>:
> Let's say a character of 150 ASCII code. Which looks like a hypen.
>
> When I retrieve the value of that field it gives me a question mark
> character instead of that 150 ASCII code character.
>
> What could be the possible reason of this?
Perhaps the ODBC driver thinks SQL_ASCII means ASCII and therefore
discards all bytes > 127. On PostgreSQL SQL_ASCII really means
SQL_ANYTHING, so to speak. Try to use for the database the encoding
you really use.
Markus Bertheau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: mbertheau.pg@googlemail.com, cpc@cybees.com
Subject: Re: PostgreSQL Handling of Special Characters
In-Reply-To: <684362e10603192009s28a0afe4m@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox