(mysql.info.gz) MyODBC bug report

Info Catalog

(mysql.info.gz) MyODBC Forum

(mysql.info.gz) MyODBC Introduction

(mysql.info.gz) MyODBC patch submission

 
 23.1.1.9 How to Report MyODBC Problems or Bugs
 ..............................................
 
 If you encounter difficulties or problems with MyODBC, you should start
 by making a log file from the `ODBC Manager' (the log you get when
 requesting logs from `ODBC ADMIN') and MyODBC. The procedure for doing
 this is described in  MyODBC trace.
 
 Check the MyODBC trace file to find out what could be wrong.  You
 should be able to determine what statements were issued by searching for
 the string `>mysql_real_query' in the `myodbc.log' file.
 
 You should also try issuing the statements from the `mysql' client
 program or from `admndemo'. This will help you determine whether the
 error is in MyODBC or MySQL.
 
 If you find out something is wrong, please only send the relevant rows
 (maximum 40 rows) to the `myodbc' mailing list.   Mailing-list.
 Please never send the whole MyODBC or ODBC log file!
 
 If you are unable to find out what's wrong, the last option is to
 create an archive in `tar' or Zip format that contains a MyODBC trace
 file, the ODBC log file, and a `README' file that explains the problem.
 You can send this to `ftp://ftp.mysql.com/pub/mysql/upload/'.  Only we
 at MySQL AB will have access to the files you upload, and we will be
 very discreet with the data.
 
 If you can create a program that also demonstrates the problem, please
 include it in the archive as well.
 
 If the program works with some other SQL server, you should include an
 ODBC log file where you do exactly the same thing in the other SQL
 server.
 
 Remember that the more information you can supply to us, the more
 likely it is that we can fix the problem.
 

Info Catalog

(mysql.info.gz) MyODBC Forum

(mysql.info.gz) MyODBC Introduction

(mysql.info.gz) MyODBC patch submission