Bug #982 Lost connection
Submitted: 3 Aug 2003 2:30 Modified: 11 Aug 2003 4:44
Reporter: Chris Van de Velde Email Updates:
Status: Not a Bug Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:3.51.06 OS:Microsoft Windows (Win 2K/server)
Assigned to: CPU Architecture:Any

[3 Aug 2003 2:30] Chris Van de Velde
Description:
I have an application that runs contiuously on my server.  Every 5 minutes it connects to the DB (somewhere on a WWW server).  99% of the time all goes well, but in some cases the connection gets lost somewhere during the processing.  Screen appears 'Connection lost during processing'.  Just clicking 'OK' and accepting the connection screen solves the problem.  But this means someone must stay present at the screen.  Is there any way I can trap this error in code (I am using Microsoft FoxPro using ODBC connection to MySql) to prevent manual intervention.

How to repeat:
Connect to the DB, execute some SQL stqtement, break the connection, execute another SQL statement, repair connection and accept all proposed screens as they are.  This explains how to force the error.  The break of the connection can happen at any time any way if the connection is made over the web

Suggested fix:
Give the programmer a possibility to trap this error in code (supplementary switch at start of the connection?)
[3 Aug 2003 6:00] Miguel Solorzano
The driver already offers Driver Trace Options for
to trap problems. Please read the Connector ODBC
Manual about.
[10 Aug 2003 8:36] Chris Van de Velde
The trace option is not available on the commercial version, only on the developer version?  Or am I getting sothing wrong?  In my ODBC settings, trace option is grayed out (not available)
[11 Aug 2003 4:44] Miguel Solorzano
The tracer driver call only is enabled in the debug version.
You can get it (only dll) at:

http://www.mysql.com/downloads/api-myodbc-3.51.html

Rename the release version and copy the debug at system32
directory renamed like the release version.