From: | "Christian Paul B(dot) Cosinas" <cpc(at)cybees(dot)com> |
---|---|
To: | "'Markus Bertheau'" <mbertheau(dot)pg(at)googlemail(dot)com> |
Cc: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL Handling of Special Characters |
Date: | 2006-03-20 05:48:03 |
Message-ID: | 002701c64be1$de30c220$1e21100a@ghwk02002147 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hi Markus,
Can you please elaborate more on this.
I'm really lost.
Thank You So Much.
-----Original Message-----
From: Markus Bertheau [mailto:mbertheau(dot)pg(at)googlemail(dot)com]
Sent: Sunday, March 19, 2006 8:09 PM
To: Christian Paul B. Cosinas
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: [SQL] PostgreSQL Handling of Special Characters
2006/3/20, Christian Paul B. Cosinas <cpc(at)cybees(dot)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
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
From | Date | Subject | |
---|---|---|---|
Next Message | Eugene E. | 2006-03-20 06:19:53 | Re: PostgreSQL Handling of Special Characters |
Previous Message | Markus Bertheau | 2006-03-20 04:09:24 | Re: PostgreSQL Handling of Special Characters |