JDBC Tutorial – The ULTIMATE Guide

This tutorial is about JDBC (Java Database Connectivity), an API provided by Oracle that allows programmers to handle different databases from Java applications: it allows developers to establish connections to databases, defines how a specific client can access a given database, provides mechanisms for reading, inserting, updating and deleting entries of data in a database and takes care of transactions composed of different SQL statements.
In this article we will explain the main JDBC components like Statements, Result Sets or Stored Procedures.

 JDBC needs drivers for the different databases that programmers may want to work with; we will explain this in detail and we will provide some examples.
JDBC comes together with Java since the beginning of times; the first release came with the JDK 1.1 on February 1997 and since then, JDBC has been an important part of Java. The main packages where JDBC is contained are http://docs.oracle.com/javase/8/docs/api/java/sql/package-summary.html and http://docs.oracle.com/javase/8/docs/api/javax/sql/package-summary.html.
All the information about the last JDBC release (4.2) and its development and maintenance can be found in the JSR 221.
All examples shown in this article have been implemented using Java 8 update 0_25 and the Eclipse SDK version Luna 4.4. At the end of the article you can download all these examples and some more!

Table of Contents

1. Components

2. Connections

3. Data types

4. Drivers

5. Databases

6. Result sets

7. Stored procedures

8. Statements

9. Batch commands

10. Transactions

11. CRUD commands

12. Java 8

13. Sql libraries built upon JDBC

14. Unit Testing

15. Summary

16. Download

17. Links

1. Components

The JDBC API allows programmers and Java applications to interact with databases. It supports executing different SQL statements and handling results coming from different data sources.
In this section we will try to summarize and list the most important JDBC components that are part of every Java application, all of them will be explained in more detail in the next chapters.

First of all, Java applications need to create and establish a connection ao a specific database. This is done using a Driver Manager, for example, one instance of the interface java.sql.DriverManager, or directly via a JDBC data source. For this purpose, the interfacejavax.sql.DataSource can be used. As already mentioned, we will explain these components in more in detail in the next chapters.

Once we are connected against a database, we can use our java.sql.Connection for executing CRUD (create, read, update, delete) SQL statements or operations. These statements are explained afterwards in this tutorial.

In order to execute these these operations, programmers can use java.sql.Statement and java.sql.PreparedStatement based classes. The last ones are more efficient when executing the same statement several times and provide other benefits that we will list in this tutorial.
The interface JDBC connection provides mechanisms to create statement instances:

1	PreparedStatement countriesStatement = connection.prepareStatement("UPDATE COUNTRIES SET NAME = ? WHERE ID = ?");

2	countriesStatement.setString(1, "Spain");

3	countriesStatement.setInt(2, 123456789);

Operations like Insert, update or delete return back the number of modified rows and nothing else:

1	// countriesStatement belongs to the class Statement, returning number of updated rows

2	int n = countriesStatement.executeUpdate();

Selection operations (queries) return results as rows inside a java.sql.ResultSet. Rows are retrieved by name or number; results metadata is also available:

1	// countriesStatement belongs to the class Statement

2	ResultSet rs = countriesStatement.executeQuery("SELECT NAME, POPULATION FROM COUNTRIES");

3	//rs contains the results in rows plus some metadata

4

...

Normally, JDBC uses connection pools for managing connections. There are different implementations for connection pools like C3P0 or DBCP. These are groups of JDBC connections that are used or borrowed from the applications when needed and released when the task is finished. There is a lot of documentation about how to use and configure connection pools within JDBC, a good tutorial can be found in the following link http://docs.oracle.com/cd/E13222_01/wls/docs81/ConsoleHelp/jdbc_connection_pools.html .

Other features are available while working with JDBC: Stored Procedures, Callable Statements, Batch Processing…all these will be described in this tutorial.

2. Connections

In order to connect to a database we need to use a java.sql.Connection object. We can do this using the getConnection() method of the java.sql.DriverManager class. This methods receives the database host and credentials as parameters.
This snippet shows how to create a connection for a local MySQL database.

1	//MySQL driver is loaded

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

3	//Connection object is created using the db host and credentials

4	Connection connect = DriverManager.getConnection("jdbc:mysql://localhost/countries?"

5	+ "user=root&password=root" );

A connection objects allows programmers to do the following actions:

Creation of JDBC Statements: Using a connection object is possible to create Statement, PreparedStatement or CallableStatement instances that offer methods to execute different SQL statements. Here is an example of the creation of a PreparedStatement:

1	//the connection conn is used to create a prepared statement with the given sql operation

2	PreparedStatement updateStmt = conn.prepareStatement( sql );

This statement can execute the sql update passed as parameter.

Offers the possibility to commit or rollback a given transaction. JDBC connection supports two different ways of working: autocommit=true and autocommit=false. The first one commits all transactions directly to the database, the second one needs an special command in order to commit or rollback the transactions. We will see this is more detail in the related chapter in this tutorial. The following piece of code shows how to change the auto commit mode of a JDBC connection :

1	//it changes the mode to auto commit=false

2	connect.setAutoCommit( false );

Possibility to get meta information about the database that is been used.

Other options like batch processing, stored procedures, etc.

We will explain all these features in detail, for the moment it is good to know what a JDBC Connection is and what can be done using JDBC Connections.

3. Data types

JDBC converts the Java data types into proper JDBC types before using them in the database. There is a default mapping between Java and JDBC data types that provides consistency between database implementations and drivers.
The following table contains these mappings:

SQL	JDBC/Java	setter	getter
VARCHAR	java.lang.String	setString	getString
CHAR	java.lang.String	setString	getString
LONGVARCHAR	java.lang.String	setString	getString
BIT	boolean	setBoolean	getBoolean
NUMERIC	BigDecimal	setBigDecimal	getBigDecimal
TINYINT	byte	setByte	getByte
SMALLINT	short	setShort	getShort
INTEGER	int	setInt	getInt
BIGINT	long	setLong	getLong
REAL	float	setFloat	getFloat
FLOAT	float	setFloat	getFloat
DOUBLE	double	setDouble	getDouble
VARBINARY	byte[ ]	setBytes	getBytes
BINARY	byte[ ]	setBytes	getBytes
DATE	java.sql.Date	setDate	getDate
TIME	java.sql.Time	setTime	getTime
TIMESTAMP	java.sql.Timestamp	setTimestamp	getTimestamp
CLOB	java.sql.Clob	setClob	getClob
BLOB	java.sql.Blob	setBlob	getBlob
ARRAY	java.sql.Array	setARRAY	getARRAY
REF	java.sql.Ref	SetRef	getRef
STRUCT	java.sql.Struct	SetStruct	getStruct

Null values are treated differently in SQL and in Java. When handling with SQL null values in Java it is good to follow some best practices like avoiding the usage of primitive types, since they cannot be null but converted to their default values like 0 for int, false for booleans, etc.
Instead of that, the usage of wrapper classes for the primitive types is recommended. The class ResultSet contains a method called wasNull() that is very useful in these scenarios. Here is an example of its usage:

1	Statement stmt = conn.createStatement( );

2	String sql = "SELECT NAME, POPULATION FROM COUNTRIES";

3	ResultSet rs = stmt.executeQuery(sql);

4

5	int id = rs.getInt(1);

6	if( rs.wasNull( ) ) {

7

id = 0;

8

}

4. Drivers

The JDBC Driver Manager, java.sql.DriverManager, is one of the most important elements of the JDBC API. It is the basic service for handling a list of JDBC Drivers. It contains mechanisms and objects that allow Java applications to connect to a desired JDBC driver. It is in charge of managing the different types of JDBC database drivers. Summarizing the main task of the Driver Manager is to be aware of the list of available drivers and to handle the connection between the specific selected driver and the database.
The most frequently used method of this class is DriverManager.getConnetion(). This method establishes a connection to a database.
Here is an example of its use:

1	// Create the connection with the default credentials

2	java.sql.Connection conn = DriverManager.getConnection("jdbc:hsqldb:mem:mydb", "SA", "" );

We can register drivers using the method DriverManager.registerDriver().:

1	new org.hsqldb.jdbc.JDBCDriver();

2	DriverManager.registerDriver( new org.hsqldb.jdbc.JDBCDriver() );

We can also load a driver by calling the Class.forName() method:

1	// Loading the HSQLDB JDBC driver

2	Class.forName( "org.hsqldb.jdbc.JDBCDriver" );

3

4

...

5

6	// connection to JDBC using mysql driver

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

The main difference is that the method registerDriver() needs that the driver is available at compile time, loading the driver class does not require that the driver is available at compile time. After JDBC 4, there is no real need of calling these methods and applications do not need to register drivers individually neither to load the driver classes. It is also not recommended to register drivers manually using the method registerDriver().
Other interesting methods of the DriverManager class are getDriver(String url), that tries to locate the driver by a given string and getDrivers() that returns an enumeration of all the drivers that has been previously registered in the Driver Manager:

1	Enumeration drivers = DriverManager.getDrivers();

2	while( drivers.hasMoreElements() )

3

{

4	Driver driver = drivers.nextElement();

5	System.out.println( driver.getClass() );

6

}

5. Databases

JDBC supports a large list of databases. It abstracts its differences and ways of working by using different Drivers. The DriverManager class is in charge of loading the proper database, after this is loaded, the code that access the database for querying and modifying data will remain (more or less) unchanged.
Here is a list of supported databases in JDBC (officially registered within Oracle): http://www.oracle.com/technetwork/java/index-136695.html.
In this chapter we are going to show how to use to different databases: MySQL and HSQLDB. The first one is very well known by programmers and wide used, the second one, HSQLDB, is a database very helpful for testing purposes that offers in memory capabilities. We will see how to use both and we will discover that except of the loading of the proper JDBC driver, the rest of the application remains unchanged:
MySQL example:

01	public static void main( String[] args ) throws ClassNotFoundException, SQLException

02

{

03

04	// connection to JDBC using mysql driver

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

06	Connection connect = DriverManager.getConnection("jdbc:mysql://localhost/countries?"

07	+ "user=root&password=root" );

08

09

10	selectAll( connect );

11

12	// close resources, in case of exception resources are not properly cleared

13

...

14

15

}

16

17

/**

18	* select statement and print out results in a JDBC result set

19

*

20	* @param conn

21	* @throws SQLException

22

*/

23	private static void selectAll( java.sql.Connection conn ) throws SQLException

24

{

25	Statement statement = conn.createStatement();

26

27	ResultSet resultSet = statement.executeQuery( "select * from COUNTRIES" );

28

29	while( resultSet.next() )

30

{

31	String name = resultSet.getString( "NAME" );

32	String population = resultSet.getString( "POPULATION" );

33

34	System.out.println( "NAME: " + name );

35	System.out.println( "POPULATION: " + population );

36

}

37

38

}

In memory (HSQLDB) example:

01	public static void main( String[] args ) throws ClassNotFoundException, SQLException

02

{

03

04	// Loading the HSQLDB JDBC driver

05	Class.forName( "org.hsqldb.jdbc.JDBCDriver" );

06

07	// Create the connection with the default credentials

08	java.sql.Connection conn = DriverManager.getConnection( "jdbc:hsqldb:mem:mydb", "SA", "" );

09

10	// Create a table in memory

11	String countriesTableSQL = "create memory table COUNTRIES (NAME varchar(256) not null primary key, POPULATION varchar(256) not null);";

12

13	// execute the statement using JDBC normal Statements

14	Statement st = conn.createStatement();

15	st.execute( countriesTableSQL );

16

17	// nothing is in the database because it is just in memory, non persistent

18	selectAll( conn );

19

20	// after some insertions, the select shows something different, in the next execution these

21	// entries will not be there

22	insertRows( conn );

23	selectAll( conn );

24

25

}

26

27

...

28

29

/**

30	* select statement and print out results in a JDBC result set

31

*

32	* @param conn

33	* @throws SQLException

34

*/

35	private static void selectAll( java.sql.Connection conn ) throws SQLException

36

{

37	Statement statement = conn.createStatement();

38

39	ResultSet resultSet = statement.executeQuery( "select * from COUNTRIES" );

40

41	while( resultSet.next() )

42

{

43	String name = resultSet.getString( "NAME" );

44	String population = resultSet.getString( "POPULATION" );

45

46	System.out.println( "NAME: " + name );

47	System.out.println( "POPULATION: " + population );

48

}

49

50

}

As we can see in last programs, the code of the selectAll methods is completely the same, only the JDBC Driver loading and connection creation changes; you can imagine how powerful this is when working in different environments. The HSQLDB version of the code contains also the piece of code in charge of creating the in memory database and inserting some rows, but this is just for showing and clarity purposes and can be done differently.
 

6. Result sets

The class java.sql.ResultSet represents a result set of database table. It is created, normally; by executing an SQL query (select statement using Statement or PreparedStatement). It contains rows of data, where the data is stored. These data can be accessed by index (starting by 1) or by attribute name:

01	// creating the result set

02	ResultSet resultSet = statement.executeQuery( "select * from COUNTRIES" );

03

04	// iterating through the results rows

05

06	while( resultSet.next() )

07

{

08	// accessing column values by index or name

09	String name = resultSet.getString( "NAME" );

10	int population = resultSet.getInt( "POPULATION" );

11

12	System.out.println( "NAME: " + name );

13	System.out.println( "POPULATION: " + population );

14

15

16	// accessing column values by index or name

17	String name = resultSet.getString( 1 );

18	int population = resultSet.getInt( 2 );

19

20	System.out.println( "NAME: " + name );

21	System.out.println( "POPULATION: " + population );

22

23

24

}

As shown before, ResultSets contain getter methods for retrieving column values for different Java types. It also contains a cursor pointing to the current row of data. Initially, the cursor is pointing before the first row. The next method moves the cursor to the next row: java.sql.ResultSet.next().
It is possible to create ResultSets with default properties like a cursor that moves forward only and that is not updatable. If programmers would like to use other kind of properties he can specify so in the creation of the Statement that is going to produce the result sets by changing the arguments passed:

1

/**

2	* indicating result sets properties that will be created from this statement: type,

3	* concunrrency and holdability

4

*/

5	Statement statement = conn.createStatement( ResultSet. TYPE_SCROLL_INSENSITIVE,

6	ResultSet.CONCUR_UPDATABLE, ResultSet.CLOSE_CURSORS_AT_COMMIT );

Using this kind of result sets it is possible to move the cursor in both directions and to update or insert new data into the database using the result set with this purpose. 

7. Stored procedures

In this chapter we are going to explain what stored procedures are and how we can use them within JDBC. For the examples we are going to use MySQL based stored procedures.
Stored procedures are sets of SQL statements as part of a logical unit of executiion and performing a defined task. They are very useful while encapsulating a group of operations to be executed on a database.
First of all we are going to create a procedure in our MySQL database, following script will help us with this task:

01	delimiter //

02

03	CREATE PROCEDURE spanish (OUT population_out INT)

04

BEGIN

05	SELECT COUNT(*) INTO population_out FROM countries;

06

END//

07

08

09	delimiter ;

10

11	CALL simpleproc(@a);

Basically the script above creates a procedure called Spanish with one output attribute of the type int and without input parameters. The procedure returns the count of all countries in the database.
Once we have created the procedure we can work with it from our Java applications.In order to call Stored Procedures we need to use special statements of the interface java.sql.CallableStatement, these statements allow programmers to execute stored procedures indicating the output attributes and input parameters to be used. In our simple example, only output attributes are configured. Here is an example:

01	CallableStatement callableStatement = null;

02

03	// the procedure should be created in the database

04	String spanishProcedure = "{call spanish(?)}";

05

06	// callable statement is used

07	callableStatement = connect.prepareCall( spanishProcedure );

08

09	// out parameters, also in parameters are possible, not in this case

10	callableStatement.registerOutParameter( 1, java.sql.Types.VARCHAR );

11

12	// execute using the callable statement method executeUpdate

13	callableStatement.executeUpdate();

14

15	// attributes are retrieved by index

16	String total = callableStatement.getString( 1 );

17

18	System.out.println( "amount of spanish countries " + total );

We can appreciate how to indicate where to store the output of the procedure and how to execute it using the method java.sql.PreparedStatement.executeUpdate(). Stored procedures are supported in most of the databases but their syntax and behavior may differ, that is why there may be differences in the Java applications handling stored procedures depending on the databases where the procedures are stored. 

8. Statements

As already mentioned in this tutorial, JDBC uses the interface java.sql.Statement to execute different SQL queries and operations like insert, update or delete. This is the basic interface that contains all the basic methods like java.sql.Statement.executeQuery(String) or java.sql.Statement.executeUpdate(String).
Implementations of this interface are recommended when programmers do not need to execute same query multiple times or when queries and statements do not need to be parameterized. In general, we can say that this interface is suitable when executing DDL statements (Create, Alter, Drop). These statements are not executed multiple times normally and do not need to support different parameters.
In case programmers need better efficiency when repeating SQL queries or parameterization they should use java.sql.PreparedStatement. This interface inherits the basic statement interface mentioned before and offers parameterization. Because of this functionalitiy, this interface is safer against SQL injection attacks. Here is a piece of code showing an example of this interface:

01	System.out.println( "Updating rows for " + name + "..." );

02

03	String sql = "UPDATE COUNTRIES SET POPULATION=? WHERE NAME=?";

04

05	PreparedStatement updateStmt = conn.prepareStatement( sql );

06

07	// Bind values into the parameters.

08	updateStmt.setInt( 1, 10000000 ); // population

09	updateStmt.setString( 2, name ); // name

10

11	// update prepared statement using executeUpdate

12	int numberRows = updateStmt.executeUpdate();

13

14	System.out.println( numberRows + " rows updated..." );

Another benefit of using prepared statements is the possibility to handle non standard objects by using the setObject() method. Here is an example:

01	PreparedStatement updateStmt2 = conn.prepareStatement( sql );

02

03	// Bind values into the parameters using setObject, can be used for any kind and type of

04	// parameter.

05	updateStmt2.setObject( 1, 10000000 ); // population

06	updateStmt2.setObject( 2, name ); // name

07

08	// update prepared statement using executeUpdate

09	numberRows = updateStmt2.executeUpdate();

10

11	System.out.println( numberRows + " rows updated..." );

12	updateStmt2.close();

As mentioned in the chapter related to stored procedures, another interface is available for this purpose, it is called java.sql.CallableStatement and extends the PreparedStatement one.
 

9. Batch commands

JDBC offers the possibility to execute a list of SQL statements as a batch, that is, all in a row. Depending on what type of Statements the programmers are using the code may differ but the general idea is the same. In the next snippet is shown how to use batch processing with java.sql.Statement:

01	Statement statement = null;

02

03	statement = connect.createStatement();

04

05	// adding batchs to the statement

06	statement.addBatch( "update COUNTRIES set POPULATION=9000000 where NAME='USA'" );

07	statement.addBatch( "update COUNTRIES set POPULATION=9000000 where NAME='GERMANY'" );

08	statement.addBatch( "update COUNTRIES set POPULATION=9000000 where NAME='ARGENTINA'" );

09

10	// usage of the executeBatch method

11	int[] recordsUpdated = statement.executeBatch();

12

13	int total = 0;

14	for( int recordUpdated : recordsUpdated )

15

{

16	total += recordUpdated;

17

}

18

19	System.out.println( "total records updated by batch " + total );

And using java.sql.PreparedStatement:

01	String sql = "update COUNTRIES set POPULATION=? where NAME=?";

02

03	PreparedStatement preparedStatement = null;

04

05	preparedStatement = connect.prepareStatement( sql );

06

07	preparedStatement.setObject( 1, 1000000 );

08	preparedStatement.setObject( 2, "SPAIN" );

09

10	// adding batches

11	preparedStatement.addBatch();

12

13	preparedStatement.setObject( 1, 1000000 );

14	preparedStatement.setObject( 2, "USA" );

15

16	// adding batches

17	preparedStatement.addBatch();

18

19	// executing all batchs

20	int[] updatedRecords = preparedStatement.executeBatch();

21	int total = 0;

22	for( int recordUpdated : updatedRecords )

23

{

24	total += recordUpdated;

25

}

26

27	System.out.println( "total records updated by batch " + total );

We can see that the differences are basically the way the SQL query parameters are used and how the queries are built, but the idea of executing several statements on one row is the same. In the first case by using the method java.sql.Statement.executeBatch(), using java.sql.PreparedStatement.addBatch() and java.sql.Statement.executeBatch() in the second one.
 

10. Transactions

JDBC supports transactions and contains methods and functionalities to implement transaction based applications. We are going to list the most important ones in this chapter.

java.sql.Connection.setAutoCommit(boolean): This method receives a Boolean as parameter, in case of true (which is the default behavior), all SQL statements will be persisted automatically in the database. In case of false, changes will not be persisted automatically, this will be done by using the method java.sql.Connection.commit().

java.sql.Connection.commit(). This method can be only used if the auto commit is set to false or disabled; that is, it only works on non automatic commit mode. When executing this method all changes since last commit / rollback will be persisted in the database.

java.sql.Connection.rollback(). This method can be used only when auto commit is disabled. It undoes or reverts all changes done in the current transaction.

And here is an example of usage where we can see how to disable the auto commit mode by using the method setAutoCommit(false). All changes are committed when calling commit() and current transaction changes are rolled back by using the method rollback():

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

02	Connection connect = null;

03

try

04

{

05	// connection to JDBC using mysql driver

06	connect = DriverManager.getConnection( "jdbc:mysql://localhost/countries?"

07	+ "user=root&password=root" );

08	connect.setAutoCommit( false );

09

10	System.out.println( "Inserting row for Japan..." );

11	String sql = "INSERT INTO COUNTRIES (NAME,POPULATION) VALUES ('JAPAN', '45000000')";

12

13	PreparedStatement insertStmt = connect.prepareStatement( sql );

14

15	// insert statement using executeUpdate

16	insertStmt.executeUpdate( sql );

17	connect.rollback();

18

19	System.out.println( "Updating row for Japan..." );

20	// update statement using executeUpdate -> will cause an error, update will not be

21	// executed becaues the row does not exist

22	sql = "UPDATE COUNTRIES SET POPULATION='1000000' WHERE NAME='JAPAN'";

23	PreparedStatement updateStmt = connect.prepareStatement( sql );

24

25	updateStmt.executeUpdate( sql );

26	connect.commit();

27

28

}

29	catch( SQLException ex )

30

{

31	ex.printStackTrace();

32	//undoes all changes in current transaction

33	connect.rollback();

34

}

35

finally

36

{

37	connect.close();

38

}

11. CRUD commands

CRUD comes from Create, Read, Update and Delete. JDBC supports all these operations and commands, in this chapter we are going to show difference snippets of Java code performing all of them:
Create Statement. It is possible to create databases using JDBC, here is an example of creation of a in memory database:

1	// Create a table in memory

2	String countriesTableSQL = "create memory table COUNTRIES (NAME varchar(256) not null primary key, POPULATION varchar(256) not null);";

3

4	// execute the statement using JDBC normal Statements

5	Statement st = conn.createStatement();

6	st.execute( countriesTableSQL );

Insert Statement. Inserts are supported in JDBC. Programmers can use normal SQL syntax and pass them to the different statement classes that JDBC offers like Statement, PreparedStatement or CallableStatement. Here are a couple of examples:

01	Statement insertStmt = conn.createStatement();

02

03	String sql = "INSERT INTO COUNTRIES (NAME,POPULATION) VALUES ('SPAIN', '45Mill')";

04	insertStmt.executeUpdate( sql );

05

06	sql = "INSERT INTO COUNTRIES (NAME,POPULATION) VALUES ('USA', '200Mill')";

07	insertStmt.executeUpdate( sql );

08

09	sql = "INSERT INTO COUNTRIES (NAME,POPULATION) VALUES ('GERMANY', '90Mill')";

10	insertStmt.executeUpdate( sql );

These statements return the number of inserted rows. The same is applicable to update statements, here is an example of how to update a set of rows in a database:

1	System.out.println( "Updating rows for " + name + "..." );

2

3	Statement updateStmt = conn.createStatement();

4

5	// update statement using executeUpdate

6	String sql = "UPDATE COUNTRIES SET POPULATION='10000000' WHERE NAME='" + name + "'";

7	int numberRows = updateStmt.executeUpdate( sql );

8

9	System.out.println( numberRows + " rows updated..." );

The output would be:

1	Updating rows for SPAIN...

2	4 rows updated...

Select Statement. It is possible to execute any (almost) kind of SQL query using JDBC statements. Here is a very simple example that reads all the rows of a given table and prints them out in the standard console:

01	Statement statement = conn.createStatement();

02

03	ResultSet resultSet = statement.executeQuery( "select * from COUNTRIES" );

04

05	while( resultSet.next() )

06

{

07	String name = resultSet.getString( "NAME" );

08	String population = resultSet.getString( "POPULATION" );

09	System.out.println( "NAME: " + name );

10	System.out.println( "POPULATION: " + population );

11

}

The output of this would be (depending on the database state):

1	NAME: GERMANY

2	POPULATION: 90Mill

3	NAME: SPAIN

4	POPULATION: 45Mill

5

NAME: USA

6	POPULATION: 200Mill

Delete statement. Finally, JDBC supports deletion of rows and dropping of tables and other SQL elements. Here is a snippet showing the deletion of all rows with an specific criteria (in this case, the name has to be “JAPAN”):

1	System.out.println( "Deleting rows for JAPAN..." );

2	String sql = "DELETE FROM COUNTRIES WHERE NAME='JAPAN'";

3	PreparedStatement deleteStmt = connect.prepareStatement( sql );

4

5	// delete statement using executeUpdate

6	int numberRows = deleteStmt.executeUpdate( sql );

7

8	System.out.println( numberRows + " rows deleted..." );

Delete statements return the number of affected rows, in this case the output would be (depending on the database state):

1	Deleting rows for JAPAN...

2	0 rows deleted...

These examples are all very simple ones; they have been written for learning purposes but you can imagine that you can execute more complicated SQL queries just by changing the argument passed to the executeQuery() or executeUpdate() methods.  

12. Java 8

Java 8 does not contain any major change related to JDBC or the JDBC framework. But several features of Java 8 can be applied when working with JDBC with very good results. We are going to show some of them. For example it is possible to execute select queries in a very different way as we are used to. Here is an example of how we do it without Java 8 features, it is more or less the same as we did in all our examples during this article:

01	// we always need to write this code

02	System.out.println( "using Java 7" );

03	// connection to JDBC using mysql driver

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

05	Connection connect = DriverManager.getConnection( "jdbc:mysql://localhost/countries?"

06	+ "user=root&password=root" );

07

08	// select query

09	PreparedStatement statement = connect.prepareStatement( "select * from COUNTRIES" );

10	ResultSet resultSet = statement.executeQuery();

11

12	// iterating results

13	while( resultSet.next() )

14

{

15	// access via name

16	Object name = resultSet.getObject( 1 );

17	Object population = resultSet.getObject( 2 );

18

19	System.out.println( "Name: " + name );

20	System.out.println( "Population: " + population );

21

}

22

23	// close resources, in case of exception resources are not properly cleared

24	resultSet.close();

25	statement.close();

26	connect.close();

And here is a version that does the same but using Lambdas.

1	// select method is called and lambda expression is provided, this expression will be used

2	// in the handle method of the functional interface

3	select( connect, "select * from COUNTRIES", ( resultSet ) -> {

4	System.out.println( resultSet.getObject( 1 ) );

5	System.out.println( resultSet.getObject( 2 ) );

6

} );

The piece of code shown above contains a select method call where the first parameter is the Connection object, the second parameter is an SQL query and the third one is a Lambda expression. This Lambda expression receives one parameter (instance of ResultSet) and prints out its first two attributes, but anything can be done with this result set in the body of the Lambda expression. Here is the implementation of the select() method:

01	public static void select( Connection connect, String sql, ResultSetHandler handler ) throws SQLException

02

{

03	PreparedStatement statement = connect.prepareStatement( sql );

04

05	try (ResultSet rs = statement.executeQuery())

06

{

07	while( rs.next() )

08

{

09	handler.handle( rs );

10

}

11

12

}

13

}

And the functional interface ResultSetHandler:

01	@FunctionalInterface

02	public interface ResultSetHandler

03

{

04

05

/**

06	* This method will be executed by the lambda expression

07

*

08	* @param resultSet

09	* @throws SQLException

10

*/

11	public void handle( ResultSet resultSet ) throws SQLException;

12

13

}

We can see here that the code is clearer and reduced drastically (or not) when using some of the new Java 8 features. 

13. Sql libraries built upon JDBC

JDBC is used by several well known Java libraries to build their APIs. In this section we are going to list some of them:

HSQLDB (Hyper SQL Database) is a relational database management system that offers in memory and persistent storage. It has a JDBC driver (as shown in some of the examples). It is very useful for testing purposes because of its non persistent features and supports almost all the SQL core features. For more information please visit http://hsqldb.org/

DBUnit is an extension of JUnit. It is very useful for unit testing when databases are involved. This framework takes care of the databases state between tests and abstract several databases properties when testing. For downloading the sources and more documentation please visit http://www.dbunit.org

DBUtils is an Apache Commons library implemented with the goal of make the usage of JDBC much easier. Some of the features that this library contains are: clean up of resources, reduction of code quantity, easier and automatic population of result sets. This library is small, transparent and fast and should be used by developers who want to work directly with JDBC. Java 1.6 or higher is needed for using this library. For more documentation http://commons.apache.org/proper/commons-dbutils/

Spring Data also contains a module related to JDBC. It is called Spring Data JDBC Extensions. It offers support for the most used features of JDBC. It offers special features for working with Oracle databases. If you want to learn more about this library please visit http://projects.spring.io/spring-data-jdbc-ext/

JOOQ is a very interesting framework from the company datageekery that uses JDBC; it generates Java code from SQL databases and offers an API to establish JDBC connections, querying data and handle the results in an easy way. For more information please visit their git hub account: https://github.com/jOOQ/jOOL .

14. Unit Testing

When it comes to unit testing and databases there are always several questions open:

What environment do we use for testing?

Do we test with real data?

Or do we use synthetic generated data?

How do we test our databases without the proper credentials?

Several libraries can help us with these tasks. In this chapter we are going to list some of them and provide some useful links where more information can be found:

DBUnit: as stated before, DBUnit is a testing framework that works in collaboration with Junit. For more information http://dbunit.org

TestNG: This testing framework covers a lot of testing scenarios like unit testing, functional testing, integration testing, etc. It is based on annotations. For more information about this framework please visit their web site: http://testng.org/doc/index.html

JOOQ. This framewok provides JDBC mocking and testing capabilities. It is very well documented and easy to use. For more information please visit http://jooq.org

15. Summary

JDBC (Java Database Connectivity) is the standard API for Database connectivity between Java and a huge number of databases and data sources (from SQL based databases to Excel spreadsheets). In this tutorial we tried to explain the JDBC architecture and how to use it; we listed the main components that JDBC uses and we listed some of the drivers for different wide used databases like MySql.
The most important points to remember are:

Drivers are components that enable a Java application to work with a database. JDBC requires drivers for every specific database. A list of available drivers for JDBC can be found at http://www.oracle.com/technetwork/java/index-136695.html.

SQL statements are sent directly to the database servers every time. JDBC contains a mechanism called PreparedStatement with predetermined execution path that provides more efficiency and better use of the resources.

Result Sets are the representation used for rows coming out from a query.

Stored Procedures are sets of SQL statements grouped together, they can be called by name without the need to call each separately.

Transactions are groups of SQL statements. A transaction ends when commit() or rollback() are called. This grouping allow different to work in parallel.

CRUD commands are create, read, update and delete commands. JDBC provide mechanisms to execute these commands.

The tutorial contains some information related to new possibilities coming out with Java 8 related to JDBC like JOOQ; we also mentioned some important libraries implemented using JDBC like Spring-Data or Apache DBUtils.
  

16. Download

Download
You can download the full source code of this tutorial here: jdbc_ultimate_tutorial.

17. Links

Apart of all the links and resources pointed during this article, if you are interested in learning more about the JDBC API and its features and mechanisms, the best up to date information source that you can find are the ones in the official Oracle web site:

http://docs.oracle.com/javase/8/docs/api/javax/sql/package-summary.html

http://docs.oracle.com/javase/8/docs/api/javax/sql/package-summary.html 

SOURCE