Re: Bug or not about ASCII and Multi-Byte character set

As I have said a number of times now, DO NOT USE ASCII FOR NON-ASCII DATA!!!

Whilst some apps like pgAdmin may do what you expect, other apps and interfaces may not.

Instead of ASCII, use the correct encoding for your data, or try Unicode if unsure.

Regards, Dave

-----Original Message-----
From: "Josef Springer"<Josef.Springer@JOOPS.COM>
Sent: 14/08/05 18:49:49
To: "ZF"<zf.tech@gmail.com>
Cc: "pgsql-odbc@postgresql.org"<pgsql-odbc@postgresql.org>
Subject: Re: [ODBC] Bug or not about ASCII and Multi-Byte character set

Multibyte characters are written correctly but readed wrong by the ODBC
driver. Seems to work on WinXP clients right. Only Win2k clients may
have this problem. This bug may be corrected in PostgreSQL 8.1.

Josef Springer

ZF wrote:

>version: psqlodbc 08.00.0101 and 08.00.0102
>
>The server database encoding is ASCII in win2000. After inserting several multi-byte characters with pgAdmin3(version:
1.2.1),i found the odbc driver can't provide the right data (application is written in visual c++ and call ODBC API to
accessdb server). All displayed multi-byte char set data were not correct but the ASCII data was right. However,
pgAdmin3can correctly insert and select all data .  
>
>Then i read the "mylog" file and found the multi-byte data have been got correctly from server.
>Is it possible that some function (maybe the converting function) have a little bug?
>
>
>P.S.
>if the server db encoding is UNICODE and producing a new psqlodbc.dll through  deleting all SQL*W function in
'psqlodbc_win32.def'file, i got Delphi applications using odbc driver can show all right data. 
>---------------------------(end of broadcast)---------------------------
>TIP 9: In versions below 8.0, the planner will ignore your desire to
>       choose an index scan if your joining column's datatypes do not
>       match
>

--

mit freundlichen Grüssen,
Josef Springer
(Gescha"ftsleitung)

<cid:part1.05000701.06060503@netscape.com> -- the software company --

Orlando-di-Lasso Str. 2
D-85640 Putzbrunn

Tel. ++49(0)89 600 6920
Fax ++49(0)89 600 69220
mailto Josef.Springer@joops.com <mailto:Josef.Springer@joops.com>
Website http://www.joops.com





-----Unmodified Original Message-----
Multibyte characters are written correctly but readed wrong by the ODBC
driver. Seems to work on WinXP clients right. Only Win2k clients may
have this problem. This bug may be corrected in PostgreSQL 8.1.

Josef Springer

ZF wrote:

>version: psqlodbc 08.00.0101 and 08.00.0102
>
>The server database encoding is ASCII in win2000. After inserting several multi-byte characters with pgAdmin3(version:
1.2.1),i found the odbc driver can't provide the right data (application is written in visual c++ and call ODBC API to
accessdb server). All displayed multi-byte char set data were not correct but the ASCII data was right. However,
pgAdmin3can correctly insert and select all data .  
>
>Then i read the "mylog" file and found the multi-byte data have been got correctly from server.
>Is it possible that some function (maybe the converting function) have a little bug?
>
>
>P.S.
>if the server db encoding is UNICODE and producing a new psqlodbc.dll through  deleting all SQL*W function in
'psqlodbc_win32.def'file, i got Delphi applications using odbc driver can show all right data. 
>---------------------------(end of broadcast)---------------------------
>TIP 9: In versions below 8.0, the planner will ignore your desire to
>       choose an index scan if your joining column's datatypes do not
>       match
>

--

mit freundlichen Grüssen,
Josef Springer
(Gescha"ftsleitung)

<cid:part1.05000701.06060503@netscape.com> -- the software company --

Orlando-di-Lasso Str. 2
D-85640 Putzbrunn

Tel. ++49(0)89 600 6920
Fax ++49(0)89 600 69220
mailto Josef.Springer@joops.com <mailto:Josef.Springer@joops.com>
Website http://www.joops.com