i18n in JDBC driver
От | Martin Kuba |
---|---|
Тема | i18n in JDBC driver |
Дата | |
Msg-id | 3801E929.F98D9A17@inet.cz обсуждение исходный текст |
Ответ на | JDBC: ResultSet.updateString(int columnIndex, String x) when is this going to be implemented? (Nigel Tamplin <nigel.tamplin@metica.com>) |
Список | pgsql-interfaces |
Hi, I want to upgrade from v6.4.2 to v6.5.2, but I have some problems with character encoding: In 6.4.2 the "String(bytes[])" constructor was used for converting database 8-bit characters to Java 16-bit characters, so client's JVM default encoding was used instead of database encoding. I had to change the source code of the JDBC driver to use it. Now I have found this in CHANGELOG in v6.5.2: "Wed May 19 00:20:00 BST 1999 - Internationalisation now done. Surprising that there's 68 error messages in the driver;-)" so I think that it should be corrected now in v6.5.2. But in postgresql/jdbc2/ResultSet.java on line 151 there is still "return new String(this_row[columnIndex - 1]);" which means that the bug is NOT corrected ! I need a client with "Cp1250" default encoding (Czech WindowsNT) to be able to connect to a database with "LATIN2" encoding (Linux). Now the ResultData.getString() method returns wrong characters. So, am I missing something ? What does it mean "Internationalisation now done" ? Martin -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ INET, a.s. Mgr. Martin Kuba Kralovopolska 139 e-mail: makub@inet.cz 601 12 Brno WWW: http://www.inet.cz/~makub/CzechRepublic tel: +420-5-41242414/33 -------------------------------------------------------------------- PGP fingerprint = D8 57 47 E5 36 D2 C1 A1 C3 48 B2 59 00 58 42 27http://wwwkeys.cz.pgp.net:11371/pks/lookup?op=index&search=makub --------------------------------------------------------------------
В списке pgsql-interfaces по дате отправления: