Java Database Connectivity

Java Database Connectivity (JDBC) is an application

programming interface (API) for the programming language
JDBC
Java, which defines how a client may access a database. It is Developer(s) Oracle Corporation
a Java-based data access technology used for Java database Stable release JDBC 4.3
/
connectivity. It is part of the Java Standard Edition platform,
September 21, 2017
from Oracle Corporation. It provides methods to query and
update data in a database, and is oriented toward relational Operating system Cross-platform
databases. A JDBC-to-ODBC bridge enables connections to Type Data access API
any ODBC-accessible data source in the Java virtual machine
Website JDBC API Guide (htt
(JVM) host environment.
ps://docs.oracle.co
m/javase/8/docs/tec
hnotes/guides/jdbc)
Contents
History and implementation
Functionality
Examples
JDBC drivers
Types
Sources
See also
References
External links

History and implementation

Sun Microsystems released JDBC as part of Java Development Kit (JDK) 1.1 on February 19, 1997.[1]
Since then it has been part of the Java Platform, Standard Edition (Java SE).

The JDBC classes are contained in the Java package java.sql (https://docs.oracle.com/
javase/10/docs/api/java/sql/package-summary.html) and javax.sql (http
s://docs.oracle.com/javase/10/docs/api/javax/sql/package-summary.ht
ml).

Starting with version 3.1, JDBC has been developed under the Java Community Process. JSR 54 specifies
JDBC 3.0 (included in J2SE 1.4), JSR 114 specifies the JDBC Rowset additions, and JSR 221 is the
specification of JDBC 4.0 (included in Java SE 6).[2]

JDBC 4.1, is specified by a maintenance release 1 of JSR 221[3] and is included in Java SE 7.[4]

JDBC 4.2, is specified by a maintenance release 2 of JSR 221[5] and is included in Java SE 8.[6]
The latest version, JDBC 4.3, is specified by a maintenance release 3 of JSR 221[7] and is included in Java
SE 9.[8]

Functionality
JDBC ('Java Database Connectivity') allows multiple implementations to exist and be used by the same
application. The API provides a mechanism for dynamically loading the correct Java packages and
registering them with the JDBC Driver Manager. The Driver Manager is used as a connection factory for
creating JDBC connections.

JDBC connections support creating and executing statements. These may be update statements such as
SQL's CREATE, INSERT, UPDATE and DELETE, or they may be query statements such as SELECT.
Additionally, stored procedures may be invoked through a JDBC connection. JDBC represents statements
using one of the following classes:

Statement (https://docs.oracle.com/javase/10/docs/api/java/sql/St
atement.html) – the statement is sent to the database server each and every time.
PreparedStatement (https://docs.oracle.com/javase/10/docs/api/jav
a/sql/PreparedStatement.html) – 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.
CallableStatement (https://docs.oracle.com/javase/10/docs/api/jav
a/sql/CallableStatement.html) – used for executing stored procedures on the
database.

Update statements such as INSERT, UPDATE and DELETE return an update count that indicates how
many rows were affected in the database. 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 javax.sql (https://docs.oracle.com/

javase/10/docs/api/javax/sql/package-summary.html).

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 connection. 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.

Connection conn = DriverManager.getConnection(

"jdbc:somejdbcvendor:other data needed by some jdbc

vendor",

"myLogin",

"myPassword");

 try {

/* you use the connection here */

Host database types which Java can
} finally {
convert to with a function
//It's important to close the connection when you
are done with it
Oracle Datatype setXXX() Methods
try {

conn.close();
CHAR setString()
} catch (Throwable e) { /* Propagate the original
exception
VARCHAR2 setString()
instead of this one that
you want just logged */
setBigDecimal()
logger.warn("Could not close JDBC
Connection",e);
setBoolean()
}

}
setByte()

setShort()
NUMBER
Starting from Java SE 7 you can use Java's try-with-resources (htt setInt()
p://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourc
setLong()
eClose.html) statement to make the above code simpler:
setFloat()
try (Connection conn = DriverManager.getConnection(

setDouble()
"jdbc:somejdbcvendor:other data needed by some jdbc
vendor",

INTEGER setInt()
"myLogin",

"myPassword")) {

FLOAT setDouble()
/* you use the connection here */

} // the VM will take care of closing the connection

CLOB setClob()

BLOB setBlob()
Once a connection is established, a statement can be created.
RAW setBytes()

try (Statement stmt = conn.createStatement()) {

LONGRAW setBytes()
stmt.executeUpdate("INSERT INTO MyTable(name) VALUES
('my name')");
setDate()
}

DATE setTime()

setTimestamp()
Note that Connections, Statements, and ResultSets often tie up
operating system resources such as sockets or file descriptors. In
the case of Connections to remote database servers, further resources are tied up on the server, e.g., cursors
for currently open ResultSets.
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.

try (Statement stmt = conn.createStatement();

ResultSet rs = stmt.executeQuery("SELECT * FROM MyTable")

) {

while (rs.next()) {

int numColumns = rs.getMetaData().getColumnCount();

for (int i = 1; i <= numColumns; i++) {

// Column numbers start at 1.

// Also there are many methods on the result set to return

// the column as a particular type. Refer to the Sun documentation

// for the list of valid conversions.

System.out.println( "COLUMN " + i + " = " + rs.getObject(i));

An example of a PreparedStatement query, using conn and class from first example.
 try (PreparedStatement ps =

conn.prepareStatement("SELECT i.*, j.* FROM Omega i, Zappa j WHERE i.name = ? AND j.num
= ?")

) {

// In the SQL statement being prepared, each question mark is a placeholder

// that must be replaced with a value you provide through a "set" method invocation.

// The following two method calls replace the two placeholders; the first is

// replaced by a string value, and the second by an integer value.

ps.setString(1, "Poor Yorick");

ps.setInt(2, 8008);

// The ResultSet, rs, conveys the result of executing the SQL statement.

// Each time you call rs.next(), an internal row pointer, or cursor,

// is advanced to the next row of the result. The cursor initially is

// positioned before the first row.

try (ResultSet rs = ps.executeQuery()) {

while (rs.next()) {

int numColumns = rs.getMetaData().getColumnCount();

for (int i = 1; i <= numColumns; i++) {

// Column numbers start at 1.

// Also there are many methods on the result set to return

// the column as a particular type. Refer to the Sun documentation

// for the list of valid conversions.

System.out.println("COLUMN " + i + " = " + rs.getObject(i));

} // for

} // while

} // try

} // try

If a database operation fails, JDBC raises an SQLException (https://docs.oracle.com/j

avase/10/docs/api/java/sql/SQLException.html). 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 SQLException be translated into an application domain exception (an unchecked
one) that eventually results in a transaction rollback and a notification to the user.

An example of a database transaction:

boolean autoCommitDefault = conn.getAutoCommit();

try {

conn.setAutoCommit(false);

/* You execute statements against conn here transactionally */

conn.commit();

} catch (Throwable e) {

try { conn.rollback(); } catch (Throwable e) { logger.warn("Could not rollback

transaction", e); }

throw e;

} finally {

try { conn.setAutoCommit(autoCommitDefault); } catch (Throwable e) { logger.warn("Could

not restore AutoCommit setting",e); }

For an example of a CallableStatement (to call stored procedures in the database), see the JDBC
API Guide (https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/getstart/callablestatement.html)
documentation.

import java.sql.Connection;

import java.sql.DriverManager;

import java.sql.Statement;

public class Mydb1 {

static String URL = "jdbc:mysql://localhost/mydb";

public static void main(String[] args) {

 try {

Class.forName("com.mysql.jdbc.Driver");

Connection conn = DriverManager.getConnection(URL, "root", "root");

Statement stmt = conn.createStatement();

String sql = "INSERT INTO emp1 VALUES ('pctb5361', 'kiril', 'john', 968666668)";

stmt.executeUpdate(sql);

System.out.println("Inserted records into the table...");

} catch (Exception e) {

e.printStackTrace();

JDBC drivers
JDBC drivers are client-side adapters (installed on the client machine, not on the server) 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. (Note: In JDBC 4.2,
JDBC-ODBC bridge has been removed[9])
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 (depending on whether the database itself
is implemented in Java or not). An example of this is the KPRB (Kernel Program Bundled) driver[10]
supplied with Oracle RDBMS. "jdbc:default:connection" offers a relatively standard way of making such a
connection (at least the Oracle database and Apache Derby support it). 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.

Sources
Oracle provides a list of some JDBC drivers and vendors (http://www.oracle.com/technetwor
k/java/index-136695.html)
Simba Technologies ships an SDK for building custom JDBC Drivers for any
custom/proprietary relational data source
CData Software ships type 4 JDBC Drivers for various applications, databases, and Web
APIs.[11]
 RSSBus Type 4 JDBC Drivers for applications, databases, and web services[12]
DataDirect Technologies provides a comprehensive suite of fast Type 4 JDBC drivers for all
major database they advertise as Type 5[13]
IDS Software provides a Type 3 JDBC driver for concurrent access to all major databases.
Supported features include resultset caching, SSL encryption, custom data source, dbShield
JDBaccess is a Java persistence library for MySQL and Oracle which defines major
database access operations in an easy usable API above JDBC
JNetDirect provides a suite of fully Sun J2EE certified high-performance JDBC drivers.
JDBCR4 is a service program written by Scott Klement to allow access to JDBC from RPG
on the IBM i.[14]
HSQLDB is a RDBMS with a JDBC driver and is available under a BSD license.
SchemaCrawler[15] is an open source API that leverages JDBC, and makes database
metadata available as plain old Java objects (POJOs)

See also
GNU Data Access (GDA)
JDBCFacade
Open Database Connectivity (ODBC)
Object–relational mapping (ORM)

References
1. "Sun Ships JDK 1.1 -- Javabeans Included" (https://web.archive.org/web/20080210044125/
http://www.sun.com/smi/Press/sunflash/1997-02/sunflash.970219.0001.xml). www.sun.com.
Sun Microsystems. 1997-02-19. Archived from the original (http://www.sun.com/smi/Press/su
nflash/1997-02/sunflash.970219.0001.xml) on 2008-02-10. Retrieved 2010-02-15. "February
19, 1997 - The JDK 1.1 [...] is now available [...]. This release of the JDK includes: [...]
Robust new features including JDBC for database connectivity"
2. JDBC API Specification Version: 4.0 (http://java.sun.com/products/jdbc/download.html#core
spec40).
3. "The Java Community Process(SM) Program - communityprocess - mrel" (http://jcp.org/abou
tJava/communityprocess/mrel/jsr221/index.html). jcp.org. Retrieved 22 March 2018.
4. "JDBC 4.1" (http://docs.oracle.com/javase/7/docs/technotes/guides/jdbc/jdbc_41.html).
docs.oracle.com. Retrieved 22 March 2018.
5. "The Java Community Process(SM) Program - communityprocess - mrel" (https://jcp.org/abo
utJava/communityprocess/mrel/jsr221/index2.html). jcp.org. Retrieved 22 March 2018.
6. "JDBC 4.2" (http://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/jdbc_42.html).
docs.oracle.com. Retrieved 22 March 2018.
7. "The Java Community Process(SM) Program - communityprocess - mrel" (https://jcp.org/abo
utJava/communityprocess/mrel/jsr221/index3.html). jcp.org. Retrieved 22 March 2018.
8. "java.sql (Java SE 9 & JDK 9)" (http://docs.oracle.com/javase/9/docs/api/java/sql/package-s
ummary.html). docs.oracle.com. Retrieved 22 March 2018.
9. "Java JDBC API" (https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/).
docs.oracle.com. Retrieved 22 March 2018.
10. Greenwald, Rick; Stackowiak, Robert; Stern, Jonathan (1999). Oracle Essentials: Oracle
Database 10g (https://books.google.com/books?id=CTebAgAAQBAJ). Essentials Series
(3 ed.). Sebastopol, California: O'Reilly Media, Inc. (published 2004). p. 318.
ISBN 9780596005856. Retrieved 2016-11-03. "The in-database JDBC driver (JDBC KPRB)
[:] Java code uses the JDBC KPRB (Kernel Program Bundled) version to access SQL on the
same server."
11. "JDBC Drivers - CData Software" (http://www.cdata.com/jdbc/). CData Software. Retrieved
22 March 2018.
12. "JDBC Drivers - CData Software" (http://www.rssbus.com/jdbc/). CData Software. Retrieved
22 March 2018.
13. "New Type 5 JDBC Driver — DataDirect Connect" (http://www.datadirect.com/products/featu
res/data-connectivity/type-5-jdbc/index.html).
14. "Access External Databases from RPG with JDBCR4 Meat of the Matter" (http://iprodevelop
er.com/rpg-programming/access-external-databases-rpg-jdbcr4). 28 June 2012. Retrieved
12 April 2016.
15. Sualeh Fatehi. "SchemaCrawler" (https://github.com/schemacrawler/SchemaCrawler).
SourceForge.

External links
JDBC API Guide (https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc) This
documentation has examples where the JDBC resources are not closed appropriately
(swallowing primary exceptions and being able to cause NullPointerExceptions) and has
code prone to SQL injection
java.sql (https://docs.oracle.com/javase/10/docs/api/java/sql/pac
kage-summary.html) API Javadoc documentation
javax.sql (https://docs.oracle.com/javase/10/docs/api/javax/sql/p
ackage-summary.html) API Javadoc documentation
O/R Broker (https://web.archive.org/web/20160111210342/http://orbroker.org/) Scala JDBC
framework
SqlTool (http://www.hsqldb.org/doc/2.0/util-guide/sqltool-chapt.html) Open source,
command-line, generic JDBC client utility. Works with any JDBC-supporting database.
JDBC URL Strings and related information of All Databases. (http://codeoftheday.blogspot.c
om/2012/12/java-database-connectivity-jdbc-url.html)

Retrieved from "https://en.wikipedia.org/w/index.php?title=Java_Database_Connectivity&oldid=1028709910"

This page was last edited on 15 June 2021, at 15:18 (UTC).

Text is available under the Creative Commons Attribution-ShareAlike License;

additional terms may apply. By using
this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia
Foundation, Inc., a non-profit organization.