The data base is SQL_ASCHII
I guess the locale is whatever it defaults to when you install from rpm on
redhat as4 not sure?
lc_messages = 'en_US.UTF-8' # locale for system error message
lc_monetary = 'en_US.UTF-8' # locale for monetary formatting
lc_numeric = 'en_US.UTF-8' # locale for number formatting
lc_time = 'en_US.UTF-8' # locale for time formatting
The client is a win2k box.
I can see the chars look ok when I view using pgadmin.
.net was displaying them ok.
The old odbc driver was displaying them ok.
Just the new ODBC driver is doing something to them to make them appear as
In any event I switched to the old driver and the site is ok.
I am very busy with after conversion repairs, but maybe later I can take a
closer look at if there is a better way (I am brain dead at the moment 75
hours last week and looking like that this week).
Unfortunately I am still having severe issues with speed and may need to use
my 2 proc SQL server for some reporting.
2520 Trailmate Dr
Sarasota, Florida 34243
Tel. 941-753-7111 ext 305
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.
From: Marko Ristola [mailto:marko(dot)ristola(at)kolumbus(dot)fi]
Sent: Wednesday, May 11, 2005 1:17 PM
To: Joel Fradkin
Subject: Re: [ODBC] encoding
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.
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
>display correctly (I amusing asp).
>2520 Trailmate Dr
>Sarasota, Florida 34243
>Tel. 941-753-7111 ext 305
>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.
In response to
pgsql-odbc by date
|Next:||From: charlie clark||Date: 2005-05-11 19:22:42|
|Subject: PostgreSQL, ODBC and long strings|
|Previous:||From: Marko Ristola||Date: 2005-05-11 18:16:35|
|Subject: Re: encoding|