Summary: Java database connection architecture is a standard method for Java applications to connect to the database. JDBC is an API for Java programmers, and is an interface model for the service provider that implements a database connection. As an API, JDBC provides a standard interface for program development, and provides standard methods for the implementation of database vendors and third-party middleware vendors. JDBC uses existing SQL standards and supports bridging between the other database connection criteria, such as ODBC. JDBC implements all of these-oriented targets and has a simple, strict type definition and high-performance interface.
How to choose a suitable JDBC product? About JDBC's latest information, interested readers can check the official website of JDBC - Javasoft's homepage, its URL is: http://java.sun.com/products/jdbc 1. JavaSoft Framework
JavaSoft offers three JDBC product components that are part of Java Development Kit (JDK): JDBC Driver Manager, JDBC Driver Test Kit, and JDBC-ODBC Bridge.
The JDBC driver manager is the pillar of the JDBC architecture. It is actually very small, it is very simple; its main role is to connect the Java application to the correct JDBC driver, and then exit.
The JDBC Driver Test Kit provides a certain credibility to make the JDBC driver run your program. Only drivers tested by JDBC driver are considered to be a JDBC standard TM.
The JDBC-ODBC bridge allows the ODBC driver to be used as a JDBC driver. Its implementation provides a way for JDBC's rapid development, and its long-term goal provides a way to access certain uncommon DBMSs (if these uncommon DBMS unpreceptible JDBCs). 2. Type of JDBC driver
Currently a common JDBC driver can be divided into the following four types:
(1) JDBC-ODBC bridge plus ODBC driver
JavaSoft Bridge products provide JDBC access using 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. Therefore, this type of driver is best suited for enterprise network (this network client installation is not the main issue), or the three-layer structure of the three-layer structure written in Java.
(2) Local API
This type of driver converts the JDBC call 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 not related to DBMS, and then this protocol 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 into network protocols 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.
According to experts expect (3), (4) drivers will become the first method of accessing the database from the JDBC. (1), (2) The class driver is used as a transition scheme before the direct pure Java driver is not listed. For subsection (1), (2) drivers may have some variants, which require a connector, but usually these are more uncomfortable solutions. (3), (4) drivers provide all the advantages of Java, including automatic installation (for example, download the driver) by using the AppleTAppletAppletApplet using the JDBC driver. 3. The JDBC driver has now available in dozens of (1) classes, which can be used in combination with the JavaSoft bridge to the ODBC driver driver. About more than 10 drivers belonging to the species (2) are written based on the local API of DBMS. Only a few drivers belonging to a type (3), the first batch of providers are SCO, Openhorizon, Visigenic and WebLogic. In addition, the leading provider of JavaSoft and database connections Intersolv also cooperated to develop JDBC-ODBC Bridge and JDBC Driver Test Kit.
