Bug #2624 SQLExecDirect() throws exception when dealing with special characters
Submitted: 3 Feb 2004 4:30 Modified: 21 Jul 2004 19:49
Reporter: SINISA MILIVOJEVIC Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S2 (Serious)
Version:3.51 OS:Windows (Windows)
Assigned to: CPU Architecture:Any

[3 Feb 2004 4:30] SINISA MILIVOJEVIC 
Description:
SQLExecDirect() throws exception when dealing with special characters.  Exception is  thrown while the code is executed under Microsoft Visual studio.  It won't throw exception if running under DOS console.
 
 
MYSQL server: 4.0.16
MYODBC:  3.51.6.0
OS:  Win 2000 Server/Workstation.

How to repeat:
Files uploaded
[3 Feb 2004 4:32] MySQL Verification Team 
Loaded 'C:\WINNT\SYSTEM32\wshtcpip.dll', no matching symbolic information found.
 First-chance exception in console.exe (ARKMYODBC3.DLL): 0xC0000005: Access Violation.
  
 The content of table 'xyz':
  
 mysql> select name from xyz;
 +---------------------+
 | name                |
 +---------------------+
 | ?üé?üä?üå?üê?üè.jpn |
 +---------------------+
 1 row in set (0.00 sec)
  
 mysql> select hex(name) from xyz;
 +----------------------------------------+
 | hex(name)                              |
 +----------------------------------------+
 | E38182E38184E38186E38188E3818A2E6A706E |
 +----------------------------------------+
 1 row in set (0.12 sec)
[5 Feb 2004 15:29] MySQL Verification Team 
I tested your sample application without to repeat your behavior
reported. Please if you are using the MyODBC debug version try
to use the release version and report if the issue continues.
Thanks.
[10 Feb 2004 12:04] MySQL Verification Team 
Related to SAFEMALLOC flag compiling issue.
[21 Jul 2004 19:49] Timothy Smith 
Fixed in latest release.