About JDBC

1

JDBC-ODBC bridge

Translates JDBC calls into ODBC calls, and sends them to the ODBC driver.

Advantages Allows access to many different databases.

Disadvantages The ODBC driver, and possibly the client database libraries, must reside on the ColdFusion server computer. Performance is also below par.

Macromedia does not recommend this driver type unless your application requires specific features of these drivers.

2

Native-API/partly Java driver

Converts JDBC calls into database-specific calls.

Advantages Better performance than Type 1 Driver.

Disadvantages The vendor's client database libraries must reside on the same computer as ColdFusion.

Macromedia does not recommend this driver type unless your application requires specific features of these drivers, such as the Unicode support offered by the ColdFusion MX Microsoft Access with Unicode driver.

3

JDBC-Net pure Java driver

Translates JDBC calls to the middle-tier server, which then translates the request to the database-specific native-connectivity interface.

Advantages No need for vendor's database libraries to be present on client computer. Can be tailored for small size (faster loading).

Disadvantages Database-specific code must be executed in the middle-tier.

ColdFusion MX includes an ODBC socket type 3 driver for use with Microsoft Access databases and ODBC data sources.

4

Native-protocol/all-Java driver

Converts JDBC calls into the network protocol used directly by the database.

Advantages Fast performance. No special software needed on the computer on which you run ColdFusion MX.

Disadvantages Many of these protocols are proprietary, requiring a different driver for each database.

ColdFusion MX includes type 4 drivers for many popular DBMSs, however, not all DBMSs are supported in ColdFusion MX Standard Edition.