Connector/Odbc Examples - Oracle 5.0 Reference Manual

TraceFile
can also use
then follow the instructions for tracing
20.1.4.8.4. Enabling a Connector/ODBC Log
To generate a Connector/ODBC log, do the following:
1. Within Windows, enable the
connect/configure screen. The log is written to file C:\myodbc.log. If the trace option is not
remembered when you are going back to the above screen, it means that you are not using the
myodbcd.dll
On Mac OS X, Unix, or if you are using a DSN-less connection, either supply
connection string, or set the corresponding keyword/value pair in the DSN.
2. Start your application and try to get it to fail. Then check the Connector/ODBC trace file to find out
what could be wrong.
If you need help determining what is wrong, see
Support".

20.1.5. Connector/ODBC Examples

Once you have configured a DSN to provide access to a database, how you access and use that
connection is dependent on the application or programming language. As ODBC is a standardized
interface, any application or language that supports ODBC can use the DSN and connect to the
configured database.
20.1.5.1. Basic Connector/ODBC Application Steps
Interacting with a MySQL server from an applications using the Connector/ODBC typically involves the
following operations:
• Configure the Connector/ODBC DSN.
• Connect to MySQL server.
• Initialization operations.
• Execute SQL statements.
• Retrieve results.
• Perform transactions.
• Disconnect from the server.
Most applications use some variation of these steps. The basic application steps are shown in the
following diagram:
Connector/ODBC Examples
specifies the name and full path of the trace file and
or for and
1 YES ON 0
Trace Connector/ODBC
driver, see Section 20.1.4.3.3, "Troubleshooting ODBC Connection
or for OFF. If you are using
NO
calls at HOWTO-ODBCConfig.
unixODBC
option flag in the Connector/ODBC
Section 20.1.8.1, "Connector/ODBC Community
1772
is set to or OFF. You
Trace ON
from unixODBC,
ODBCConfig
Problems".
OPTION=4
in the