Java Database Connectivity

Java Database Connectivity is an application programming interface for the Java programming language which defines how a client may access a database. It is a Java-based data access technology used for Java database connectivity. It is part of the Java Standard Edition platform, from Oracle Corporation. It provides methods to query and update data in a database, and is oriented toward relational databases. A JDBC-to-ODBC bridge enables connections to any ODBC-accessible data source in the Java virtual machine host environment.

WWW Official Site

History and implementation

Sun Microsystems released JDBC as part of Java Development Kit 1.1 on February 19, 1997.
Since then it has been part of the Java Platform, Standard Edition.
The JDBC classes are contained in the Java package and, as well as a few other classes elsewhere. Everything involved in JDBC is exported through module java.sql.
Starting with version 3.1, JDBC has been developed under the Java Community Process. JSR 54 specifies JDBC 3.0, JSR 114 specifies the JDBC Rowset additions, and JSR 221 is the specification of JDBC 4.0.
JDBC 4.1, is specified by a maintenance release 1 of JSR 221 and is included in Java SE 7.
JDBC 4.2, is specified by a maintenance release 2 of JSR 221 and is included in Java SE 8.
The latest version, JDBC 4.3, is specified by a maintenance release 3 of JSR 221 and is included in Java SE 9.

JDBC version	Java version	Release Type	Release date
1.1	JDK 1.1	Main	1997-02-19.
	J2SE 1.4	Main	2002-05-09
	Java SE 6	Main	2006-12-11
	Java SE 7	Maintenance	2011-10-13
	Java SE 8	Maintenance	2014-03-04
	Java SE 9	Maintenance	2017-09-21

Functionality

Since JDBC is mostly a collection of interface definitions and specifications, it allows multiple implementations of these interfaces to exist and be used by the same application at runtime. The API provides a mechanism for dynamically loading the correct Java packages and registering them with the JDBC Driver Manager. is used as a factory for creating JDBC connections.
JDBC connections support creating and executing statements. JDBC connections support update statements such as SQL's [Create (SQL)|], [Insert (SQL)|], [Update (SQL)|] and [Delete (SQL)|], or query statements such as [Select (SQL)|]. Additionally, stored procedures may be invoked through a JDBC connection. JDBC represents statements using one of the following classes:

- the is sent to the database server each and every time. In other words, the methods are executed using SQL statements to obtain a object containing the data.
- is a subinterface of the interface. The statement is cached and then the execution path is pre-determined on the database server, allowing it to be executed multiple times in an efficient manner. is used to execute pre-compiled SQL statements. Running pre-compiled statements increases statement execution efficiency and performance. The is often used for dynamic statement where some input parameters must be passed into the target database. The allows the dynamic query to vary depending on the query parameter.
- is a subinterface of the interface. It is used for executing stored procedures on the database. Both input and output parameters must be passed into the database for stored procedures.

Update statements such as INSERT, UPDATE and DELETE return an update count indicating the number of rows affected in the database as an integer. These statements do not return any other information.
Query statements return a JDBC row result set. The row result set is used to walk over the result set. Individual columns in a row are retrieved either by name or by column number. There may be any number of rows in the result set. The row result set has metadata that describes the names of the columns and their types.
There is an extension to the basic JDBC API in the.
JDBC connections are often managed via a connection pool rather than obtained directly from the driver.

Examples

When a Java application needs a database connection, one of the DriverManager.getConnection methods is used to create a JDBC. The URL used is dependent upon the particular database and JDBC driver. It will always begin with the jdbc: protocol, but the rest is up to the particular vendor.

import java.sql.Connection;
import java.sql.DriverManager;
Connection conn = DriverManager.getConnection;
try finally

Starting from Java SE 7, one can use Java's statement to simplify the above code:

import java.sql.Connection;
import java.sql.DriverManager;
try
// conn.close automatically called
// the connection will automatically close after leaving the try block

Once a connection is established, a can be created.

import java.sql.Statement;
try )

Note that s, s, and s often tie up operating system resources such as sockets or file descriptors. In the case of s to remote database servers, further resources are tied up on the server, e.g. cursors for currently open s.
It is vital to close any JDBC object as soon as it has played its part;
garbage collection should not be relied upon.
The above try-with-resources construct is a code pattern that obviates this.
Data is retrieved from the database using a database query mechanism. The example below shows creating a statement and executing a query.

import java.sql.ResultSet;
import java.sql.Statement;
try ;
ResultSet rs = stmt.executeQuery
)

The following code is an example of a PreparedStatement query which uses conn and class from the first example:

import java.sql.PreparedStatement;
import java.sql.ResultSet;
try

If a database operation fails, JDBC raises an. There is typically very little one can do to recover from such an error, apart from logging it with as much detail as possible. It is recommended that the be translated into an application domain exception that eventually results in a transaction rollback and a notification to the user.
The following code is an example of a database transaction:

import java.sql.SQLException;
boolean autoCommitDefault = conn.getAutoCommit;
try catch finally

For an example of a CallableStatement, see the documentation.

package org.wikipedia.examples;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.Statement;
public class DatabaseExample

JDBC drivers

JDBC drivers are client-side adapters that convert requests from Java programs to a protocol that the DBMS can understand.

Types

Commercial and free drivers provide connectivity to most relational-database servers. These drivers fall into one of the following types:

Type 1 that calls native code of the locally available ODBC driver.
Type 2 that calls database vendor native library on a client side. This code then talks to database over the network.
Type 3, the pure-java driver that talks with the server-side middleware that then talks to the database.
Type 4, the pure-java driver that uses database native protocol.

Note also a type called an internal JDBC driver - a driver embedded with JRE in Java-enabled SQL databases. It is used for Java stored procedures. This does not fit into the classification scheme above, although it would likely resemble either a type 2 or type 4 driver. An example of this is the KPRB driver
supplied with Oracle RDBMS. "jdbc:default:connection" offers a relatively standard way of making such a connection. However, in the case of an internal JDBC driver, the JDBC client actually runs as part of the database being accessed, and so can access data directly rather than through network protocols.