Connector/ODBC Notes and Tips
1805
This alternative method requires that
sql_auto_is_null
[493]
variable is not set to 0. See
Section 5.1.4, “Server System Variables”
.
See also
Section 20.6.13.3, “How to Get the Unique ID for the Last Inserted Row”
.
20.1.7.1.2. Dynamic Cursor Support
Support for the
dynamic cursor
is provided in Connector/ODBC 3.51, but dynamic cursors are not
enabled by default. You can enable this function within Windows by selecting the
Enable Dynamic
Cursor
check box within the ODBC Data Source Administrator.
On other platforms, you can enable the dynamic cursor by adding
32
to the
OPTION
value when
creating the DSN.
20.1.7.1.3. Connector/ODBC Performance
The Connector/ODBC driver has been optimized to provide very fast performance. If you experience
problems with the performance of Connector/ODBC, or notice a large amount of disk activity for simple
queries, there are a number of aspects to check:
• Ensure that
ODBC Tracing
is not enabled. With tracing enabled, a lot of information is recorded in
the tracing file by the ODBC Manager. You can check, and disable, tracing within Windows using the
Tracing panel of the ODBC Data Source Administrator. Within Mac OS X, check the Tracing panel of
ODBC Administrator. See
Section 20.1.4.8, “Getting an ODBC Trace File”
.
• Make sure you are using the standard version of the driver, and not the debug version. The debug
version includes additional checks and reporting measures.
• Disable the Connector/ODBC driver trace and query logs. These options are enabled for each DSN,
so make sure to examine only the DSN that you are using in your application. Within Windows, you
can disable the Connector/ODBC and query logs by modifying the DSN configuration. Within Mac
OS X and Unix, ensure that the driver trace (option value 4) and query logging (option value 524288)
are not enabled.
20.1.7.1.4. Setting ODBC Query Timeout in Windows
For more information on how to set the query timeout on Microsoft Windows when executing
queries through an ODBC connection, read the Microsoft knowledgebase document at
http://
support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B153756
.
20.1.7.2. Connector/ODBC Application-Specific Tips
Most programs should work with Connector/ODBC, but for each of those listed here, there are specific
notes and tips to improve or enhance the way you work with Connector/ODBC and these applications.
With all applications, ensure that you are using the latest Connector/ODBC drivers, ODBC Manager
and any supporting libraries and interfaces used by your application. For example, on Windows, using
the latest version of Microsoft Data Access Components (MDAC) will improve the compatibility with
ODBC in general, and with the Connector/ODBC driver.
20.1.7.2.1. Using Connector/ODBC with Microsoft Applications
The majority of Microsoft applications have been tested with Connector/ODBC, including Microsoft
Office, Microsoft Access and the various programming languages supported within ASP and Microsoft
Visual Studio.
20.1.7.2.1.1. Microsoft Access
To improve the integration between Microsoft Access and MySQL through Connector/ODBC:
• For all versions of Access, enable the Connector/ODBC
Return matching rows
option. For
Access 2.0, also enable the
Simulate ODBC 1.0
option.
Summary of Contents for 5.0
Page 1: ...MySQL 5 0 Reference Manual ...
Page 18: ...xviii ...
Page 60: ...40 ...
Page 396: ...376 ...
Page 578: ...558 ...
Page 636: ...616 ...
Page 844: ...824 ...
Page 1234: ...1214 ...
Page 1427: ...MySQL Proxy Scripting 1407 ...
Page 1734: ...1714 ...
Page 1752: ...1732 ...
Page 1783: ...Configuring Connector ODBC 1763 ...
Page 1793: ...Connector ODBC Examples 1773 ...
Page 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Page 2850: ...2830 ...
Page 2854: ...2834 ...
Page 2928: ...2908 ...
Page 3000: ...2980 ...
Page 3122: ...3102 ...
Page 3126: ...3106 ...
Page 3174: ...3154 ...
Page 3232: ...3212 ...