Re: Bug or not about ASCII and Multi-Byte character set
От | Josef Springer |
---|---|
Тема | Re: Bug or not about ASCII and Multi-Byte character set |
Дата | |
Msg-id | 42FF833E.5040601@joops.com обсуждение исходный текст |
Ответ на | Bug or not about ASCII and Multi-Byte character set ("ZF" <zf.tech@gmail.com>) |
Список | pgsql-odbc |
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:
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 access db server). All displayed multi-byte char set data were not correct but the ASCII data was right. However, pgAdmin3 can 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 be low 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
(Geschäftsleitung)
-- 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 |
Website | http://www.joops.com |
Вложения
В списке pgsql-odbc по дате отправления: