Types of JDBC drivers
A quite popular question in java interviews is that what and how many different types of JDBC drivers exists? The answer must be known to lot of people in java development world but i am sure there are many which are not aware of this.
There are 4 types of JDBC technology drivers:
1. JDBC-ODBC bridge: This provides JDBC API access via ODBC(Open Datbase connectivity) driver. In this case ODBC native library or native database client library should be present on the machine from where you are trying to access database using JDBC API. This also requires extra configuraton for ODBC driver on client machine.The JDBC-ODBC Bridge driver is recommended for use in prototyping efforts and for cases where no other JDBC technology-based driver exists. know more about JDBC-ODBC bridge driver.
2. Native API – Partly Java:This types of driver converts JDBC calls into calls on the client API for Oracle, Informix or other DBMS. This also requires client API libraries loaded on client machine.
3. Net-protocol fully Java: This driver driver translates JDBC API calls into a DBMS-independent net protocol which is then translated to a DBMS protocol by a server. This net server middleware is able to connect all of its Java technology-based clients to many different databases. The specific protocol used depends on the vendor. In general, this is the most flexible JDBC API alternative. It is likely that all vendors of this solution will provide products suitable for Intranet use. In order for these products to also support Internet access they must handle the additional requirements for security, access through firewalls, etc., that the Web imposes. Several vendors are adding JDBC technology-based drivers to their existing database middleware products.
4. Native-protocol fully Java: This driver converts JDBC technology calls into the network protocol used by DBMSs directly. This allows a direct call from the client machine to the DBMS server and is a practical solution for Intranet access. Since many of these protocols are proprietary the database vendors themselves will be the primary source for this style of driver. This does not require any client library on machine to access DBMS
Most Commented Posts
If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.
Comments
No comments yet.
Leave a comment