LIMITATIONS OF JDBC-ODBC BRIDGE DRIVER
Disadvantage With type 4 drivers, the user needs a different driver for each database. This allows a direct call from the client machine to the DBMS server. This type of driver is very flexible that is a single driver can actually provide access to multiple databases. Almost any database for which ODBC driver is installed, can be accessed. As we have middle tier we can do caching and load balancing.
|Date Added:||11 February 2005|
|File Size:||55.62 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Types of JDBC Drivers
Thin driver Pure Java driver It is a pure Java driver which connects all Java drivers directly to the vendor specific database protocol. Above is the code snippet which makes the select.
Developers prefer this driver only for prototyping purpose and avoid them for actual development. Please help improve it to make it understandable to non-expertswithout removing the technical details. No need to install anything on the client.
Thus the performance is considerably improved. We will discuss other types as well–in the context of each of the supported databases—for a better understanding. When using JDBC, Java programmers have the ability to request connections to a database, send queries to the database using SQL statements, and receive results for advanced processing. If the middle-tier server can in turn use Type1, Type 2 or Type 4 drivers.
This is a Type 4 driver and supports Sybase 10, 11, 12 and Because it is written entirely in Java, this driver is platform-independent. The middle-tier then translates the request to the database.
Retrieved from ” https: Universal Data Access Technology Blog. The app driver name comes from the notion that this driver will perform a native connect through a local DB2 client to a remote database, and from its package name COM.
Since the Bridge driver is jdbc-odbbc written fully in Java, Type 1 drivers are not portable.
Further, these drivers can be downloaded dynamically. User needs to make sure the JDBC driver of the database vendor is loaded onto each client machine. Type 2 driver resides on the client along with the JAVA application. For information llimitations to install the Informix driver, see http: The middle tier is responsible to converts JDBC calls directly or indirectly into vender specific database protocol.
JDBC Driver Types
Advantages It is platform independent means limitatiins Java driver. December Learn how and when to remove this template message. The results are then sent back through the reverse process. Lot of inconsistency in code as we are dealing with different vendor API.
This type of driver is very flexible that is a single driver can actually provide access to multiple databases. Architecture of Type 1 Driver Type 2: This differs from the type 4 driver in that the protocol conversion logic resides not at the client, but in the middle-tier. This driver is fully written in Java and hence Brldge.
JDBC allows a developer to write applications that is database independent. Thus, it can be used as System Store instead of the Derby database, to boost the performance of the components relying on it.
The disadvantage for using this type of driver is that it requires a separate JDBC middleware server to translate specific native-connectivity interface.
The other implication is that any application using a type 1 driver is non-portable given the binding between the driver and platform.
JDBC driver – Wikipedia
Disadvantages Performance overhead Installed on each client machine Not suitable for applet programming. There limitationd many opportunities to optimize portability, performance, and scalability. Contact links Contact Us Report a Bug.