1、JDBC-ODBC bridge plus ODBC driver: JDBC-ODBC橋驅(qū)動(dòng)程序，將JDBC調(diào)用轉(zhuǎn)換為ODBC的調(diào)用。( This combination PRovides JDBC access via ODBC drivers. ODBC binary code--and in many cases, database client code-- must be loaded on each client machine that uses a JDBC-ODBC Bridge. Sun provides a JDBC-ODBC Bridge driver, which is appropriate for eXPerimental use and for situations in which no other driver is available.)
2、Native-API partly-Java driver: 將JDBC調(diào)用轉(zhuǎn)換為對(duì)數(shù)據(jù)庫(kù)客戶端API的調(diào)用。(A native-API partly Java technology-enabled driver: This type of driver converts JDBC calls into calls on the client API for Oracle, Sybase, Informix, DB2, or other DBMS. Note that, like the bridge driver, this style of driver requires that some binary code be loaded on each client machine.)
3、 Pure Java Driver for Database Middleware: 先將JDBC調(diào)用轉(zhuǎn)換為DBMS-independent網(wǎng)絡(luò)協(xié)議，然后由服務(wù)器端的中間件轉(zhuǎn)換為具體數(shù)據(jù)庫(kù)服務(wù)器可以接收的網(wǎng)絡(luò)協(xié)議。(net-protocol fully Java technology-enabled driver #This style of driver translates JDBC calls into the middleware vendor's protocol, which is then translated to a DBMS protocol by a middleware server. The middleware provides connectivity to many different databases.)
4、Direct-to-Database Pure Java Driver: 將JDBC調(diào)用直接轉(zhuǎn)換為具體數(shù)據(jù)庫(kù)服務(wù)器可以接收的網(wǎng)絡(luò)協(xié)議。(native-protocol fully Java technology-enabled driver #This style of driver converts JDBC calls into the network protocol used directly by DBMSs, allowing a direct call from the client machine to the DBMS server and providing a practical solution for intranet access.)
