Easysoft ODBC-PostgreSQL Driver User's Guide - Technical Reference

Technical Reference for the Easysoft ODBC-PostgreSQL Driver

This section contains extra information relating to the deployment of the Easysoft ODBC-PostgreSQL Driver.

Appendix Guide

ODBC Conformance

The Easysoft ODBC-PostgreSQL Driver complies with the ODBC 3.52 specification.

The Easysoft ODBC-PostgreSQL Driver is Level 2 compliant.

ODBC API Support

All ODBC 3.52 calls are supported.

Tracing

The ODBC calls an application makes can be traced:

Within the driver manager by an application

An application can turn tracing on in the Driver Manager by using the ODBC API SQLSetConnectAttr (...,SQL_ATTR_TRACE,...).

The trace file name may also be specified with the SQLSetConnectAttr attribute SQL_ATTR_TRACEFILE.

From within the driver manager on Unix

For the unixODBC Driver Manager, add two attributes to the [ODBC] section (create one if none exists) in odbcinst.ini.

Trace = Yes

TraceFile =logfile

For example:

[ODBC]

Trace = Yes

TraceFile = /tmp/unixodbc.log

Ensure that the user who is running the application to be traced has write permission to the log file (and to the directory containing it), or no tracing information will be produced.

From within the Easysoft ODBC-PostgreSQL Driver

Driver manager trace files show all the ODBC calls applications make, their arguments and return values. Easysoft ODBC-PostgreSQL Driver driver tracing is specific to the Easysoft driver and is of most use when making a support call.

From within the Easysoft ODBC-PostgreSQL Driver on Unix

To enable Easysoft ODBC-PostgreSQL Driver logging, add a LOGFILE and a LOGGING attribute to the relevant DSN section of the odbc.ini file.

For example:

[POSTGRESQL_SAMPLE]

.

.

.

LOGFILE = /tmp/pgsql-driver.log

LOGGING = Yes

The LOGFILE value is the path and file name of the log file. The value shown in the example specifies a log file named /tmp/pgsql.log. The LOGGING value specifies the actions to log. The value shown in the example specifies that all actions should be logged.

Ensure that the user who is running the application to be traced has write permission to the log file (and to the directory containing it).