Bug #27064 Catastrophic Failure in odbc connector 3.51.14 Windows

• Submitted: 13 Mar 2007 4:54
• Modified: 3 Apr 2007 8:19
• Reporter: andrew turnbull
• Status: Can't repeat
• Category: Connector / ODBC
• Severity: S3 (Non-critical)
• Version: 3,51.14
• OS: Windows (Windows Server)
• CPU Architecture: Any

[13 Mar 2007 4:54] andrew turnbull

Description:
After upgrading connector from 3.51.6.0 none of my code that uses DSN connections works but fails with the error Catastrophic Failure on attempting to open the connection. Opening with a connection string works. I have tried going back to 3.51.9 but this also fails. The only solution is to back out to 3.51.06. This bug seems to have existed for a long time and not been fixed. Unfortunately I only found this out after upgrading

How to repeat:
Easy. Use VB6. Create a  line project
dim a as new adodb.connection
a.open("dsn=somedsn")

define the dsn then try to run the project

[3 Apr 2007 8:19] Tonci Grgin

Hi and thanks for your report.

Environment:
 - MySQL server 5.0.38BK on WinXP Pro SP2 localhost
 - MyODBC 3.51.14GA with SystemDSN (myodbc1)
 - MS VS2005 Pro

I slightly modified test case from another report. Here's the code:
        Dim I As Long
        Dim cx As New ADODB.Connection
        Dim rs As New ADODB.Recordset
        Dim stm As ADODB.Stream
        cx.ConnectionString = "DSN=myodbc1"
        '"DRIVER={MySQL ODBC 3.51 Driver};SERVER=localhost;DATABASE=test;UID=root;PWD=;OPTION=16427"
        cx.Open()
        cx.Execute("DROP TABLE IF EXISTS bug27117")
...
and, as can be observed from general query log, all works fine:
070403 10:14:57	     90 Connect     root@localhost on test
		     90 Query       SET SQL_AUTO_IS_NULL=0
		     90 Query       select database()
070403 10:15:17	     90 Query       DROP TABLE IF EXISTS bug27117

If you can provide me with more info, please reopen the report.