The JDBC driver we currently know can be divided into the following four types:
1. JDBC-ODBC Bridge Addition ODBC Driver: JavaSoft Bridge Products Provides JDBC Access with the ODBC driver. Note that the ODBC binary code (in many cases also includes database client code) is loaded on each client using the driver. This type of driver is best suited for enterprise network (this network client installation is not the main problem), or a three-layer structure of the three-layer structure written in Java 5, instructor code.
2. Local API - Some drivers written in Java: This type of driver converts JDBC calls on the client API to Oracle, Sybase, Informix, DB2, or other DBMS calls. Note that like a bridge driver, this type of driver requires some binary code to each client.
3, JDBC Network Pure Java Driver: This driver converts JDBC to a network protocol that is independent of DBMS, which is converted to a DBMS protocol by a server. This network server middleware can connect its pure Java client on a variety of different databases. The specific agreement used depends on the provider. Usually, this is the most flexible JDBC driver. It is possible that all of these solutions provide products suitable for intranet. To make these products support Internet access, they must handle the security aspects of the Web, through the additional requirements of the firewall access. Several providers are adding JDBC drivers to their existing database middleware products.
4. Local Protocol Pure Java Driver: This type of driver converts JDBC calls directly to the network protocol used by DBMS. This will allow DBMS servers directly on the client machine to be a very practical solution for Intranet access. Since many such agreements are dedicated, the database provider will be the main source, and several providers are already doing this.
The 3rd, 4-class drivers will become the preferred method of accessing the database from the JDBC. The first, 2-class drivers are used as a transition scheme before the direct pure Java driver is not listed. There may be some variations for the first, 2-class drivers (not listed in the table below), which requires a connector, but usually these are more uncomfortable solutions. Class 3, 4-Category The driver provides all the advantages of Java, including automatic installation (for example, downloading the driver) by using the Applet Applet using the JDBC driver.