From: Jan N. <jan...@gm...> - 2025-04-25 22:13:17
|
Op vr 25 apr 2025 om 16:06 schreef Ashok Nadkarni <apn...@ya...>: > > And other posts on the same (DB2 drivers not supporting UTF-8) - SQLAllocHandle of the driver on SQL_HANDLE_ENV failed when connecting to IBM-DB2 database - MATLAB Answers - MATLAB Central and windows - DB2 service does not start - Stack Overflow Those posts tell me something. First, compare the story with this Tcl ticket: <https://core.tcl-lang.org/tcl/info/0b9332722a> Tcl had the same problem 5 years ago. It got the ACP value, prepended it with "cp" and then used it as an encoding name. There is no "cp65001" encoding, it should be handled as "utf-8". My guess is that the IBM dll does the same thing. No surprise the initialisation fails. They really should fix this bug, it shouldn't be difficult. Is it already reported to them? The DB2 dll simply doesn't work in any utf-8 environment. Does that make sense? Jan Nijtmans |