[ psqlodbc-Bugs-1000692 ] Broken UTF-8 support in Version 08.02.0002

Bugs item #1000692, was opened at 2006-07-28 16:14
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000692&group_id=1000125

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: Broken UTF-8 support in Version 08.02.0002

Initial Comment:
I have an english Windows 2000 with this driver, that connects to a 8.1.4 postgres DB. Previous I use the 7.4 version.

With the old driver (I guess some 7 version, I cannot find the exat string) I could connect to 7.4 version and get UTF-8 data (in this case japanese) without any issues. I added the "SET client_encoding TO 'UTF-8' in my db connect script.

Once I upgraded to the new driver I just get ??? back from the db. From both, either the 8.1 or the 7.4. I tried the old driver on the new db, but that doesn't work either.

I also tried the Postgres "UNICODE" driver, but there I get also just ??? back.

So I had to revert my upgrade for now. Is there any debug data I can provide? Client or Server side?

----------------------------------------------------------------------

Comment By: Clemens Schwaighofer (mugbuz)
Date: 2006-09-06 16:15

Message:
I uninstalled the previous drivers and installed the new ones, but I have exactly the same problem.

I need to set the connection version to 6.4 (7.4 gives illigal characters in connection stream), but I still see just ? instead of the utf-8 characters.

are there any documents I can provide (mylog, etc) to help debugging this?

----------------------------------------------------------------------

Comment By: Hiroshi Inoue (hinoue)
Date: 2006-09-03 05:47

Message:
What application are you using ?
Anyway could you attach the Mylog output ?

regards,
Hiroshi Inoue

----------------------------------------------------------------------

Comment By: Nobody (None)
Date: 2006-09-03 04:30

Message:
That driver didn't change the output. What is the best way for me to query the db through the odbc driver to confirm proper output of UTF8? I am 99% sure the application I am currently using is correct, but I would like to rule it out to be certain.

----------------------------------------------------------------------

Comment By: Hiroshi Inoue (hinoue)
Date: 2006-09-02 11:40

Message:
> I too am having trouble with unicode driver.

Could you try the newest version 8.2.0100 ?
You can download it from
http://www.postgresql.org/ftp/odbc/versions/ .

regards,
Hiroshi Inoue

----------------------------------------------------------------------

Comment By: Nobody (None)
Date: 2006-09-02 05:48

Message:
I too am having trouble with unicode driver. I can confirm the data is utf-8, as is the db. The client is utf-8. The driver seems to break it however. Why is conn_encoding=other? Is that normal?

DSN info: DSN='asdf',server='localhost',port='5432',dbase='omgmusic',user='asdf',passwd='asdf'
onlyread='0',showoid='0',fakeoidindex='0',showsystable='0'
conn_settings='',conn_encoding='OTHER'
translation_dll='',translation_option=''

----------------------------------------------------------------------

Comment By: Clemens Schwaighofer (mugbuz)
Date: 2006-08-01 14:22

Message:
I see "SEL_C_WCHAR" popping up in the mylog file. All the data in the mylog is correct UTF-8. Just when I read the data in with the ASP code I just get question marks where before I got the correct UTF-8 data.

I have changed nothing on the system nor in the code. The only thing I did, was upgrading the PSQL drivers and since then I have this mojibake problem.

----------------------------------------------------------------------

Comment By: Ludek Finstrle (luf)
Date: 2006-07-28 16:23

Message:
Hello,

it's interesting for me how you access the data? Do you request unicode data (SQL_WCHAR) or only ansi (SQL_CHAR)?
If you don't know please send me the mylog output (odbc driver option in Global and DataSource).

Regards,

Luf

----------------------------------------------------------------------

You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000692&group_id=1000125