If you encounter difficulties or problems with Connector/ODBC, start by
making a log file from the ODBC Manager
(the
log you get when requesting logs from ODBC
ADMIN
) and Connector/ODBC. The procedure for doing this is
described in
Section 5.10, “Getting an ODBC Trace File”.
Check the Connector/ODBC trace file to find out what could be wrong.
Determine what statements were issued by searching for the
string >mysql_real_query
in the
myodbc.log
file.
Also, try issuing the statements from the
mysql client program or from
admndemo
. This helps you determine whether
the error is in Connector/ODBC or MySQL.
Ideally, include the following information with your bug report:
Operating system and version
Connector/ODBC version
ODBC Driver Manager type and version
MySQL server version
ODBC trace from Driver Manager
Connector/ODBC log file from Connector/ODBC driver
Simple reproducible sample
The more information you supply, the more likely it is that we can fix the problem.
If you are unable to find out what is wrong, the last option is
to create an archive in tar or
zip format that contains a Connector/ODBC trace
file, the ODBC log file, and a README
file
that explains the problem. Initiate a bug report for our bugs
database at http://bugs.mysql.com/, then click
the Files tab in the bug report for instructions on uploading
the archive to the bugs database. Only MySQL engineers have
access to the files you upload, and we are 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 another SQL server, include an ODBC log file where you perform exactly the same SQL statements so that we can compare the results between the two systems.
Remember that the more information you can supply to us, the more likely it is that we can fix the problem.