As a result, you need some knowledge of the application server’s configuration in order to effectively use this driver type. You can think of the application server as a JDBC “proxy,” meaning that it makes calls for the client application. This kind of driver is extremely flexible since it requires no code installed on the client and a single driver can actually provide access to multiple databases.

The socket information is then translated by the middleware application server into the call format required by the DBMS and forwarded to the database server. The JDBC clients use standard network sockets to communicate with a middleware application server.

Type 3: JDBC-Net pure Java: In a Type 3 driver, a three-tier approach is used to accessing databases.

The Oracle Call Interface (OCI) driver is an example of a Type 2 driver. If we change the Database we have to change the native API as it is specific to a database and they are mostly obsolete now but you may realize some speed increase with a Type 2 driver because it eliminates ODBC’s overhead These drivers typically provided by the database vendors and used in the same manner as the JDBC-ODBC Bridge, the vendor- specific driver must be installed on each client machine. Type 2: JDBC-Native API: In a Type 2 driver, JDBC API calls are converted into native C/C++ API calls which are unique to the database.

The JDBC-ODBC bridge that comes with JDK 1.2 is a good example of this kind of driver.

Figure 13 Type 1: JDBC-ODBC Bridge Driver

When Java first came out, this was a useful driver because most databases only supported ODBC accessīut now this type of driver is recommended only for experimental use or when no other alternative is available.

Using ODBC requires configuring on your system a Data Source Name (DSN) that represents the target database. Type 1: JDBC-ODBC Bridge Driver: In a Type 1 driver, a JDBC bridge is used to access ODBC drivers installed on each client machine.Sun has divided the implementation types into four categories, Types 1, 2, 3, and 4, which is explained below: JDBC driver implementations vary because of the wide variety of operating systems and hardware platforms in which Java operates.

Java 8 jdbc odbc bridge alternative