Bug #29886 Charset not set on configure
Submitted: 19 Jul 2007 0:50 Modified: 8 Aug 2007 23:13
Reporter: Jared S (Silver Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S2 (Serious)
Version:3.51.17 OS:Windows (Vista)
Assigned to: Jim Winstead CPU Architecture:Any
Tags: charset, configure

[19 Jul 2007 0:50] Jared S 
Description:
Hi,

as it is now, after configuration of standard ODBC connection using ODBC interface, the connection doesn't actually work, but when CHARSET='utf8' everything seems OK.

How to repeat:
1. Create new connection using ODBC
2. Pump some data through the connection

Suggested fix:
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\MyODBC]
"CHARSET"="utf8"
[19 Jul 2007 0:54] Jared S 
1st Error

Attachment: Charset1.jpg (image/pjpeg, text), 12.78 KiB.
[19 Jul 2007 0:54] Jared S 
2nd Error

Attachment: Charset2.jpg (image/pjpeg, text), 11.47 KiB.
[22 Jul 2007 18:27] Jim Winstead 
Bug #29954 was marked as a duplicate of this bug.
[22 Jul 2007 18:28] Jim Winstead 
The problem (probably, haven't totally verified to be sure) is that the setup library sets the charset to " " (an empty space) by default, and we're trying to set the charset to that. We need to make it so the setup library doesn't do that, and we need to handle it when it does happen.
[23 Jul 2007 23:05] Jared S 
Hi Jim, MyODBC seems to do very nice job of listing tables from the set database, so I am wondering if best solution is to 'ping' the server for accurate charset...

>SELECT CHARSET(USER());
[8 Aug 2007 23:13] Jared S 
3.51.18 Looks like it actually accepts a NULL charset.  Thank you whoever for the good work!