Re: Usind database with encoding UNICODE and vovel - Mailing list pgsql-odbc

From Josef Springer
Subject Re: Usind database with encoding UNICODE and vovel
Date
Msg-id 42F20B91.9060406@joops.com
Whole thread Raw
In response to Re: Usind database with encoding UNICODE and vovel  ("Dave Page" <dpage@vale-housing.co.uk>)
List pgsql-odbc
He Dave,

as other wrote, there should be an encoding problem with Windows 2000.

My Environment:
Windows 2000 internal version: 5.0.2195; SP 2
Germal locale
PostgreSQL: 8.0.3
ODBC driver: 8.00.01.01 (5. March 2005)
No MDAC

Setting the encoding in the odbc driver (DNS) has no effect.

I made some tests:
Database encoding
Client encoding
Wrinting column (äöüß)
Reading column
UNICODE
LATIN1
OK
corrupted in app
UNICODE
UNICODE
corrupted in database (writing ß -> error character is a bad UNICODE)
OK

Written data was verified with PgAdminIII

Best Regards,
Josef Springer

Dave Page wrote:
 


From: Josef Springer [mailto:Josef.Springer@JOOPS.COM]
Sent: 04 August 2005 09:45
To: Dave Page
Cc: pgsql-odbc@postgresql.org
Subject: Re: [ODBC] Usind database with encoding UNICODE and vovel
Importance: Low

Hi Dave,

thanks for quick answer.
  • I used Win2k with german locale   
I've tested in German as well now, and it still works OK 
  • Used the ODBC 08.00.0101 (psqlodbc.dll)   
You should definately use 08.01.0003. It fixes a major Unicode related bug.
 
My application works well with other databases.
Is a point of  this the reason of my problems ?

What locale settings did you use for database and client ?  
 
The database is using 'C' for everything. The clients are all default - ie. I've tried German (Germany) and English (UK).
 
Regards, Dave.

pgsql-odbc by date:

Previous
From: "Dave Page"
Date:
Subject: Re: Usind database with encoding UNICODE and vovel
Next
From: "Dave Page"
Date:
Subject: Re: Usind database with encoding UNICODE and vovel