Re: encoding - Mailing list pgsql-odbc

From Marko Ristola
Subject Re: encoding
Date
Msg-id 42824C03.6060301@kolumbus.fi
Whole thread Raw
In response to encoding  ("Joel Fradkin" <jfradkin@wazagua.com>)
Responses Re: encoding  ("Joel Fradkin" <jfradkin@wazagua.com>)
List pgsql-odbc

Hi

Database's charset must be something other than plain ASCII.
(Same thing needs to be in Windows.)

Client charset is defined by environment variables.
PostgreSQL Server charset is defined at least in database creation.

When charsets are defined correctly, the PostgreSQL does know
the charsets and can do client charset conversions.

The newest Windows ODBC driver requires correct locale settings.
Maybe the older PostgreSQL server + ODBC driver don't do any
conversions, thus they just works, in that case, when there
is no need for charset conversions.

What is you PostgreSQL server's database locale setting?
Please see documentation for "create database",
and INITDB commandline tools for charset selection.


I hope this helps. I'm interested in charset alterations in ODBC, but
I don't know the psqodbc charset alteration history, or the last version's
functionality, well enough, to give robust answers.

Marko Ristola

Joel Fradkin wrote:

>I just wanted to document a recent issue, it may be that I am not aware of
>the proper way to use encoding with the 8.0 versions of odbc.
>
>With 7.4 I was getting char codes correctly from the odbc.
>
>With version 8. (just downloaded) I had a issue on my windows 2000 servers
>displaying question marks instead of the French chars.
>
>I was testing on win2003 with 7.4, so I switched the win2k machines and they
>display correctly (I amusing asp).
>
>
>
>Joel Fradkin
>
>
>
>Wazagua, Inc.
>2520 Trailmate Dr
>Sarasota, Florida 34243
>Tel.  941-753-7111 ext 305
>
>
>
>jfradkin@wazagua.com
>www.wazagua.com
>Powered by Wazagua
>Providing you with the latest Web-based technology & advanced tools.
>C 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, Inc
> This email message is for the use of the intended recipient(s) and may
>contain confidential and privileged information.  Any unauthorized review,
>use, disclosure or distribution is prohibited.  If you are not the intended
>recipient, please contact the sender by reply email and delete and destroy
>all copies of the original message, including attachments.
>
>
>
>
>
>
>
>
>
>
>


pgsql-odbc by date:

Previous
From: "Joel Fradkin"
Date:
Subject: encoding
Next
From: "Joel Fradkin"
Date:
Subject: Re: encoding