Java Database Connectivity

Database Client/Server Methodology

The monolithic single-tire database design:

Application

Database
Library
Storage

The two-tire Database Design:

Application SQL Request

(Client) Socket Database
Database Server
Library Data reply
Storage

Three-tire Database Design:

Application SQL Request Middleware

(Client)
Database Data reply Business rules Database
Library Change Server
notification. Client-side
Library

Storage Storage
What is JDBC?

JDBC provides application developers with a single API that is uniform and database independent.

JDBC stands for Java Database Connectivity, which is a standard Java API for
database-independent connectivity between the Java programming language and a
wide range of databases.

The JDBC library includes APIs for each of the tasks commonly associated with
database usage:

Making a connection to a database

Creating SQL statements
Executing that SQL queries in the database
Viewing & modifying the resulting records

. JDBC Architecture:

The JDBC API supports both two-tier and three-tier processing models for database
access but in general JDBC Architecture consists of two layers:

1. JDBC API: This provides the application-to-JDBC Manager connection.

2. JDBC Driver API: This supports the JDBC Manager-to-Driver Connection.
3. The JDBC API uses a driver manager and database-specific drivers to provide
transparent connectivity to heterogeneous databases.
4. The JDBC driver manager ensures that the correct driver is used to access each
data source. The driver manager can support multiple concurrent drivers
connected to multiple heterogeneous databases.
5. Following is the architectural diagram, which shows the location of the driver
manager with respect to the JDBC drivers and the Java application:
Common JDBC Components:

The JDBC API provides the following interfaces and classes:

DriverManager: This class manages a list of database drivers. Matches connection

requests from the java application with the proper database driver using
communication subprotocol. The first driver that recognizes a certain subprotocol under
JDBC will be used to establish a database Connection.

Driver: This interface handles communications with the database server. You will
interact directly with Driver objects very rarely. Instead, you use a DriverManager
object, which manages objects of this type. It also abstracts the details associated with
working with Driver objects.

Connection : Interface with all methods for contacting a database. The connection
object represents the communication context, i.e., all communication with database is
through connection object only.

Statement : You use objects created from this interface to submit the SQL statements
to the database. Some derived interfaces accept parameters in addition to executing
stored procedures.

ResultSet: These objects hold data retrieved from a database after you execute an
SQL query using Statement objects. It acts as an iterator to allow you to move through
its data.

SQLException: This class handles any errors that occur in a database application.

What is JDBC Driver?

JDBC drivers implement the defined interfaces in the JDBC API for interacting with your
database server.

For example, using JDBC drivers enables you to open database connections and to
interact with it by sending SQL or database commands then receiving results with Java.

The Java.sql package that ships with JDK contains various classes with their behaviours
defined and their actual implementaions are done in third-party drivers. Third party
vendors implements the java.sql.Driver interface in their database driver.

JDBC Driver Types:

JDBC driver implementations vary because of the wide variety of operating systems
and hardware platforms in which Java operates. Sun has divided the implementation
types into four categories, Types 1, 2, 3, and 4, which is explained below:
Type 1: JDBC-ODBC Bridge Driver:

In a Type 1 driver, a JDBC bridge is used to access ODBC drivers installed on each
client machine. Using ODBC requires configuring on your system a Data Source Name
(DSN) that represents the target database.

When Java first came out, this was a useful driver because most databases only
supported ODBC access but now this type of driver is recommended only for
experimental use or when no other alternative is available.

The JDBC-ODBC Bridge that comes with JDK 1.2 is a good example of this kind of
driver.

Type 2: JDBC-Native API:

In a Type 2 driver, JDBC API calls are converted into native C/C++ API calls which are
unique to the database. These drivers are typically provided by the database vendors
and used in the same manner as the JDBC-ODBC Bridge, the vendor-specific driver
must be installed on each client machine.

If we change the Database we have to change the native API as it is specific to a

database and they are mostly obsolete now but you may realize some speed increase
with a Type 2 driver, because it eliminates ODBC's overhead.
The Oracle Call Interface (OCI) driver is an example of a Type 2 driver.

Type 3: JDBC-Net pure Java:

In a Type 3 driver, a three-tier approach is used to access databases. The JDBC clients
use standard network sockets to communicate with a middleware application server.
The socket information is then translated by the middleware application server into the
call format required by the DBMS and forwarded to the database server. This kind of
driver is extremely flexible, since it requires no code installed on the client and a single
driver can actually provide access to multiple databases.

You can think of the application server as a JDBC "proxy," meaning that it makes calls
for the client application. As a result, you need some knowledge of the application
server's configuration in order to effectively use this driver type.
Your application server might use a Type 1, 2, or 4 driver to communicate with the
database, understanding the nuances will prove helpful.

Type 100: 100% pure Java:

In, Type 4 driver, a pure Java-based driver that communicates directly with vendor's
database through socket connection. This is the highest performance driver available
for the database and is usually provided by the vendor itself. This kind of driver is
extremely flexible; you don't need to install special software on the client or server.
Further, these drivers can be downloaded dynamically.

MySQL's Connector/J driver is a Type 4 driver. Because of the proprietary nature of

their network protocols, database vendors usually supply type 4 drivers.

Which Driver should be used?

If you are accessing one type of database, such as Oracle, Sybase, or IBM, the
preferred driver type is 4.

If your Java application is accessing multiple types of databases at the same time, type
3 is the preferred driver.

Type 2 drivers are useful in situations where a type 3 or type 4 driver is not available
yet for your database.

The type 1 driver is not considered a deployment-level driver and is typically used for
development and testing purposes only.

Creating JDBC Application:

There are following six steps involved in building a JDBC application:

 1. Import the packages. Requires that you include the packages containing the
JDBC classes needed for database programming. Most often, using import
java.sql.* will suffice.
2. Register the JDBC driver. Requires that you initialize a driver so you can open
a communications channel with the database.
3. Open a connection. Requires using the DriverManager.getConnection() method
to create a Connection object, which represents a physical connection with the
database.
4. Execute a query. Requires using an object of type Statement for building and
submitting an SQL statement to the database.
5. Extract data from result set. Requires that you use the appropriate
ResultSet.getXXX() method to retrieve the data from the result set.
6. Clean up the environment. Requires explicitly closing all database resources
versus relying on the JVM's garbage collection.

JDBC - Database Connections

After you've installed the appropriate driver, it's time to establish a database
connection using JDBC.

The programming involved to establish a JDBC connection is fairly simple. Here are
these simple four steps:

1. Import JDBC Packages: Add import statements to your Java program to

import required classes in your Java code.
2. Register JDBC Driver: This step causes the JVM to load the desired driver
implementation into memory so it can fulfill your JDBC requests.
3. Database URL Formulation: This is to create a properly formatted address that
points to the database to which you wish to connect.
4. Create Connection Object: Finally, code a call to the DriverManager object's
getConnection( ) method to establish actual database connection.

Import JDBC Packages:

The Import statements tell the Java compiler where to find the classes you reference
in your code and are placed at the very beginning of your source code.

To use the standard JDBC package, which allows you to select, insert, update, and
delete data in SQL tables, add the following imports to your source code:

import java.sql.* ; // for standard JDBC programs

import java.math.* ; // for BigDecimal and BigInteger support

Register JDBC Driver:

You must register your driver in your program before you use it. Registering the driver
is the process by which the Oracle driver's class file is loaded into memory so it can be
utilized as an implementation of the JDBC interfaces.
You need to do this registration only once in your program. You can register a driver in
one of two ways.

Approach (I) - Class.forName():

The most common approach to register a driver is to use Java's Class.forName()

method to dynamically load the driver's class file into memory, which automatically
registers it. This method is preferable because it allows you to make the driver
registration configurable and portable.

The following example uses Class.forName( ) to register the Oracle driver:

try {
Class.forName("oracle.jdbc.driver.OracleDriver");
}
catch(ClassNotFoundException ex) {
System.out.println("Error: unable to load driver class!");
System.exit(1);
}

You can use getInstance() method to work around noncompliant JVMs, but then
you'll have to code for two extra Exceptions as follows:

try {
Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
}
catch(ClassNotFoundException ex) {
System.out.println("Error: unable to load driver class!");
System.exit(1);
catch(IllegalAccessException ex) {
System.out.println("Error: access problem while loading!");
System.exit(2);
catch(InstantiationException ex) {
System.out.println("Error: unable to instantiate driver!");
System.exit(3);
}

Approach (II) - DriverManager.registerDriver():

The second approach you can use to register a driver is to use the static
DriverManager.registerDriver() method.

You should use the registerDriver() method if you are using a non-JDK compliant JVM,
such as the one provided by Microsoft.

The following example uses registerDriver() to register the Oracle driver:

try {
Driver myDriver = new oracle.jdbc.driver.OracleDriver();
 DriverManager.registerDriver( myDriver );
}
catch(ClassNotFoundException ex) {
System.out.println("Error: unable to load driver class!");
System.exit(1);
}

Database URL Formulation:

After you've loaded the driver, you can establish a connection using the
DriverManager.getConnection() method. For easy reference, let me list the three
overloaded DriverManager.getConnection() methods:

1. getConnection(String url)
2. getConnection(String url, Properties prop)
3. getConnection(String url, String user, String password)

Here each form requires a database URL. A database URL is an address that points to
your database.

Formulating a database URL is where most of the problems associated with

establishing a connection occur.

Following table lists down popular JDBC driver names and database URL.

RDBMS JDBC driver name URL format

MySQL com.mysql.jdbc.Driver jdbc:mysql://hostname/ databaseName
ORACLE oracle.jdbc.driver.OracleDriver jdbc:oracle:thin:@hostname:port
Number:databaseName
DB2 COM.ibm.db2.jdbc.net.DB2Driver jdbc:db2:hostname:port
Number/databaseName
Sybase com.sybase.jdbc.SybDriver jdbc:sybase:Tds:hostname: port
Number/databaseName

All the highlighted part in URL format is static and you need to change only remaining
part as per your database setup.

Create Connection Object:

Using a database URL with a username and password:

I listed down three forms of DriverManager.getConnection() method to create a

connection object. The most commonly used form of getConnection() requires you to
pass a database URL, a username, and a password:
Assuming you are using Oracle's thin driver, you'll specify a host:port:databaseName
value for the database portion of the URL.

If you have a host at TCP/IP address 192.0.0.1 with a host name of amrood, and your
Oracle listener is configured to listen on port 1521, and your database name is EMP,
then complete database URL would then be:

jdbc:oracle:thin:@amrood:1521:EMP

Now you have to call getConnection() method with appropriate username and
password to get a Connection object as follows:

String URL = "jdbc:oracle:thin:@amrood:1521:EMP";

String USER = "username";
String PASS = "password"
Connection conn = DriverManager.getConnection(URL, USER, PASS);

Using only a database URL:

A second form of the DriverManager.getConnection( ) method requires only a database

URL:

DriverManager.getConnection(String url);

However, in this case, the database URL includes the username and password and has
the following general form:

jdbc:oracle:driver:username/password@database

So the above connection can be created as follows:

String URL = "jdbc:oracle:thin:username/password@amrood:1521:EMP";

Connection conn = DriverManager.getConnection(URL);

Using a database URL and a Properties object:

A third form of the DriverManager.getConnection( ) method requires a database URL

and a Properties object:

DriverManager.getConnection(String url, Properties info);

A Properties object holds a set of keyword-value pairs. It's used to pass driver
properties to the driver during a call to the getConnection() method.

To make the same connection made by the previous examples, use the following code:
import java.util.*;

String URL = "jdbc:oracle:thin:@amrood:1521:EMP";

Properties info = new Properties( );
info.put( "user", "username" );
info.put( "password", "password" );

Connection conn = DriverManager.getConnection(URL, info);

Closing JDBC connections:

At the end of your JDBC program, it is required explicitly close all the connections to
the database to end each database session. However, if you forget, Java's garbage
collector will close the connection when it cleans up stale objects.

Relying on garbage collection, especially in database programming, is very poor

programming practice. You should make a habit of always closing the connection with
the close() method associated with connection object.

To ensure that a connection is closed, you could provide a finally block in your code. A
finally block always executes, regardless if an exception occurs or not.

To close above opened connection you should call close() method as follows:

conn.close();

Explicitly closing a connection conserves DBMS resources, which will make your
database administrator happy.

For a better understanding, I would suggest to study our JDBC - Sample Code.

JDBC - Statements

Once a connection is obtained we can interact with the database. The JDBC Statement,
CallableStatement, and PreparedStatement interfaces define the methods and
properties that enable you to send SQL or PL/SQL commands and receive data from
your database.

They also define methods that help bridge data type differences between Java and SQL
data types used in a database.

Following table provides a summary of each interface's purpose to understand how do

you decide which interface to use?

Interfaces Recommended Use

Statement Use for general-purpose access to your database. Useful when
you are using static SQL statements at runtime. The
 Statement interface cannot accept parameters.
PreparedStatement Use when you plan to use the SQL statements many times.
The PreparedStatement interface accepts input parameters at
runtime.
CallableStatement Use when you want to access database stored procedures.
The CallableStatement interface can also accept runtime input
parameters.

The Statement Objects:

Creating Statement Object:

Before you can use a Statement object to execute a SQL statement, you need to create
one using the Connection object's createStatement( ) method, as in the following
example:

Statement stmt = null;

try {
stmt = conn.createStatement( );
. . .
}
catch (SQLException e) {
. . .
}
finally {
. . .
}

Once you've created a Statement object, you can then use it to execute a SQL
statement with one of its three execute methods.

1. boolean execute(String SQL) : Returns a boolean value of true if a ResultSet

object can be retrieved; otherwise, it returns false. Use this method to execute
SQL DDL statements or when you need to use truly dynamic SQL.
2. int executeUpdate(String SQL) : Returns the numbers of rows affected by the
execution of the SQL statement. Use this method to execute SQL statements for
which you expect to get a number of rows affected - for example, an INSERT,
UPDATE, or DELETE statement.
3. ResultSet executeQuery(String SQL) : Returns a ResultSet object. Use this
method when you expect to get a result set, as you would with a SELECT
statement.

Closing Statement Obeject:

Just as you close a Connection object to save database resources, for the same reason
you should also close the Statement object.
A simple call to the close() method will do the job. If you close the Connection object
first it will close the Statement object as well. However, you should always explicitly
close the Statement object to ensure proper cleanup.

Statement stmt = null;

try {
stmt = conn.createStatement( );
. . .
}
catch (SQLException e) {
. . .
}
finally {
stmt.close();
}

For a better understanding, I would suggest to study Statement - Example Code.

The PreparedStatement Objects:

The PreparedStatement interface extends the Statement interface which gives you
added functionality with a couple of advantages over a generic Statement object.

This statement gives you the flexibility of supplying arguments dynamically.

Creating PreparedStatement Object:

PreparedStatement pstmt = null;
try {
String SQL = "Update Employees SET age = ? WHERE id = ?";
pstmt = conn.prepareStatement(SQL);
. . .
}
catch (SQLException e) {
. . .
}
finally {
. . .
}

All parameters in JDBC are represented by the ? symbol, which is known as the
parameter marker. You must supply values for every parameter before executing the
SQL statement.

The setXXX() methods bind values to the parameters, where XXX represents the Java
data type of the value you wish to bind to the input parameter. If you forget to supply
the values, you will receive an SQLException.
Each parameter marker is referred to by its ordinal position. The first marker
represents position 1, the next position 2, and so forth. This method differs from that
of Java array indices, which start at 0.

All of the Statement object's methods for interacting with the database (a)
execute(), (b) executeQuery(), and (c) executeUpdate() also work with the
PreparedStatement object. However, the methods are modified to use SQL statements
that can take input the parameters.

Closing PreparedStatement Obeject:

Just as you close a Statement object, for the same reason you should also close the
PreparedStatement object.

A simple call to the close() method will do the job. If you close the Connection object
first it will close the PreparedStatement object as well. However, you should always
explicitly close the PreparedStatement object to ensure proper cleanup.

PreparedStatement pstmt = null;

try {
String SQL = "Update Employees SET age = ? WHERE id = ?";
pstmt = conn.prepareStatement(SQL);
. . .
}
catch (SQLException e) {
. . .
}
finally {
pstmt.close();
}

For a better understanding, I would suggest to study Prepare - Example Code.

The CallableStatement Objects:

Just as a Connection object creates the Statement and PreparedStatement objects, it

also creates the CallableStatement object which would be used to execute a call to a
database stored procedure.

Creating CallableStatement Object:

Suppose, you need to execute the following Oracle stored procedure:

CREATE OR REPLACE PROCEDURE getEmpName

(EMP_ID IN NUMBER, EMP_FIRST OUT VARCHAR) AS
BEGIN
SELECT first INTO EMP_FIRST
FROM Employees
WHERE ID = EMP_ID;
END;

NOTE: Above stored procedure has been written for Oracle, but we are working with
MySQL database so let us write same stored procedure for MySQL as follows to create
it in EMP database:

DELIMITER $$

DROP PROCEDURE IF EXISTS `EMP`.`getEmpName` $$

CREATE PROCEDURE `EMP`.`getEmpName`
(IN EMP_ID INT, OUT EMP_FIRST VARCHAR(255))
BEGIN
SELECT first INTO EMP_FIRST
FROM Employees
WHERE ID = EMP_ID;
END $$

DELIMITER ;

Three types of parameters exist: IN, OUT, and INOUT. The PreparedStatement object
only uses the IN parameter. The CallableStatement object can use all three.

Here are the definitions of each:

Parameter Description
IN A parameter whose value is unknown when the SQL
statement is created. You bind values to IN parameters with
the setXXX() methods.
OUT A parameter whose value is supplied by the SQL statement it
returns. You retrieve values from theOUT parameters with the
getXXX() methods.
INOUT A parameter that provides both input and output values. You
bind variables with the setXXX() methods and retrieve values
with the getXXX() methods.

The following code snippet shows how to employ the Connection.prepareCall()

method to instantiate a CallableStatement object based on the preceding stored
procedure:

CallableStatement cstmt = null;

try {
String SQL = "{call getEmpName (?, ?)}";
cstmt = conn.prepareCall (SQL);
. . .
}
catch (SQLException e) {
 . . .
}
finally {
. . .
}

The String variable SQL represents the stored procedure, with parameter placeholders.

Using CallableStatement objects is much like using PreparedStatement objects. You

must bind values to all parameters before executing the statement, or you will receive
an SQLException.

If you have IN parameters, just follow the same rules and techniques that apply to a
PreparedStatement object; use the setXXX() method that corresponds to the Java data
type you are binding.

When you use OUT and INOUT parameters you must employ an additional
CallableStatement method, registerOutParameter(). The registerOutParameter()
method binds the JDBC data type to the data type the stored procedure is expected to
return.

Once you call your stored procedure, you retrieve the value from the OUT parameter
with the appropriate getXXX() method. This method casts the retrieved value of SQL
type to a Java data type.

Closing CallableStatement Obeject:

Just as you close other Statement object, for the same reason you should also close
the CallableStatement object.

A simple call to the close() method will do the job. If you close the Connection object
first it will close the CallableStatement object as well. However, you should always
explicitly close the CallableStatement object to ensure proper cleanup.

CallableStatement cstmt = null;

try {
String SQL = "{call getEmpName (?, ?)}";
cstmt = conn.prepareCall (SQL);
. . .
}
catch (SQLException e) {
. . .
}
finally {
cstmt.close();
}
JDBC - Result Sets

The SQL statements that read data from a database query return the data in a result
set. The SELECT statement is the standard way to select rows from a database and
view them in a result set. The java.sql.ResultSet interface represents the result set of a
database query.

A ResultSet object maintains a cursor that points to the current row in the result set.
The term "result set" refers to the row and column data contained in a ResultSet
object.

The methods of the ResultSet interface can be broken down into three categories:

1. Navigational methods: used to move the cursor around.

2. Get methods: used to view the data in the columns of the current row being
pointed to by the cursor.
3. Update methods: used to update the data in the columns of the current row.
The updates can then be updated in the underlying database as well.

The cursor is movable based on the properties of the ResultSet. These properties are
designated when the corresponding Statement that generated the ResultSet is created.

JDBC provides following connection methods to create statements with desired

ResultSet:

1. createStatement(int RSType, int RSConcurrency);

2. prepareStatement(String SQL, int RSType, int RSConcurrency);
3. prepareCall(String sql, int RSType, int RSConcurrency);

The first argument indicate the type of a ResultSet object and the second argument is
one of two ResultSet constants for specifying whether a result set is read-only or
updatable.

Type of ResultSet:

The possible RSType are given below, If you do not specify any ResultSet type, you will
automatically get one that is TYPE_FORWARD_ONLY.

Type Description
ResultSet.TYPE_FORWARD_ONLY The cursor can only move forward in the result
set.
ResultSet.TYPE_SCROLL_INSENSITIVE The cursor can scroll forwards and backwards,
and the result set is not sensitive to changes
made by others to the database that occur
after the result set was created.
ResultSet.TYPE_SCROLL_SENSITIVE. The cursor can scroll forwards and backwards,
 and the result set is sensitive to changes made
by others to the database that occur after the
result set was created.

Concurrency of ResultSet:

The possible RSConcurrency are given below, If you do not specify any Concurrency
type, you will automatically get one that is CONCUR_READ_ONLY.

Concurrency Description
ResultSet.CONCUR_READ_ONLY Creates a read-only result set. This is the default
ResultSet.CONCUR_UPDATABLE Creates an updateable result set.

Our all the examples written so far can be written as follows which initializes a
Statement object to create a forward-only, read only ResultSet object:

try {
Statement stmt = conn.createStatement(
ResultSet.TYPE_FORWARD_ONLY,
ResultSet.CONCUR_READ_ONLY);
}
catch(Exception ex) {
....
}
finally {
....
}

Navigating a Result Set:

There are several methods in the ResultSet interface that involve moving the cursor,
including:

S.N. Methods & Description

1 public void beforeFirst() throws SQLException
Moves the cursor to just before the first row
2 public void afterLast() throws SQLException
Moves the cursor to just after the last row
3 public boolean first() throws SQLException
Moves the cursor to the first row
4 public void last() throws SQLException
Moves the cursor to the last row.
5 public boolean absolute(int row) throws SQLException
 Moves the cursor to the specified row
6 public boolean relative(int row) throws SQLException
Moves the cursor the given number of rows forward or backwards from where it
currently is pointing.
7 public boolean previous() throws SQLException
Moves the cursor to the previous row. This method returns false if the previous
row is off the result set
8 public boolean next() throws SQLException
Moves the cursor to the next row. This method returns false if there are no more
rows in the result set
9 public int getRow() throws SQLException
Returns the row number that the cursor is pointing to.
10 public void moveToInsertRow() throws SQLException
Moves the cursor to a special row in the result set that can be used to
insert a new row into the database. The current cursor location is
remembered.
11 public void moveToCurrentRow() throws SQLException
Moves the cursor back to the current row if the cursor is currently at the
insert row; otherwise, this method does nothing

For a better understanding, I would suggest to study Navigate - Example Code.

Viewing a Result Set:

The ResultSet interface contains dozens of methods for getting the data of the current
row.

There is a get method for each of the possible data types, and each get method has
two versions:

1. One that takes in a column name.

2. One that takes in a column index.

For example, if the column you are interested in viewing contains an int, you need to
use one of the getInt() methods of ResultSet:

S.N. Methods & Description

1 public int getInt(String columnName) throws SQLException
Returns the int in the current row in the column named columnName
2 public int getInt(int columnIndex) throws SQLException
Returns the int in the current row in the specified column index. The column
index starts at 1, meaning the first column of a row is 1, the second column of a
row is 2, and so on.
Similarly there are get methods in the ResultSet interface for each of the eight Java
primitive types, as well as common types such as java.lang.String, java.lang.Object,
and java.net.URL

There are also methods for getting SQL data types java.sql.Date, java.sql.Time,
java.sql.TimeStamp, java.sql.Clob, and java.sql.Blob. Check the documentation for
more information about using these SQL data types.

For a better understanding, I would suggest to study Viewing - Example Code.

Updating a Result Set:

The ResultSet interface contains a collection of update methods for updating the data
of a result set.

As with the get methods, there are two update methods for each data type:

1. One that takes in a column name.

2. One that takes in a column index.

For example, to update a String column of the current row of a result set, you would
use one of the following updateString() methods:

S.N. Methods & Description

1 public void updateString(int columnIndex, String s) throws
SQLException
Changes the String in the specified column to the value of s.
2 public void updateString(String columnName, String s) throws
SQLException
Similar to the previous method, except that the column is specified by its name
instead of its index.

There are update methods for the eight primitive data types, as well as String, Object,
URL, and the SQL data types in the java.sql package.

Updating a row in the result set changes the columns of the current row in the
ResultSet object, but not in the underlying database. To update your changes to the
row in the database, you need to invoke one of the following methods.

S.N. Methods & Description

1 public void updateRow()
Updates the current row by updating the corresponding row in the database.
2 public void deleteRow()
Deletes the current row from the database
3 public void refreshRow()
 Refreshes the data in the result set to reflect any recent changes in the database.
4 public void cancelRowUpdates()
Cancels any updates made on the current row.
5 public void insertRow()
Inserts a row into the database. This method can only be invoked when the
cursor is pointing to the insert row.

JDBC - Data Types

The JDBC driver converts the Java data type to the appropriate JDBC type before
sending it to the database. It uses a default mapping for most data types. For
example, a Java int is converted to an SQL INTEGER. Default mappings were created
to provide consistency between drivers.

The following table summarizes the default JDBC data type that the Java data type is
converted to when you call the setXXX() method of the PreparedStatement or
CallableStatement object or the ResultSet.updateXXX() method.

SQL JDBC/Java setXXX updateXXX

VARCHAR java.lang.String setString updateString
CHAR java.lang.String setString updateString
LONGVARCHAR java.lang.String setString updateString
BIT boolean setBoolean updateBoolean
NUMERIC java.math.BigDecimal setBigDecimal updateBigDecimal
TINYINT byte setByte updateByte
SMALLINT short setShort updateShort
INTEGER int setInt updateInt
BIGINT long setLong updateLong
REAL float setFloat updateFloat
FLOAT float setFloat updateFloat
DOUBLE double setDouble updateDouble
VARBINARY byte[ ] setBytes updateBytes
BINARY byte[ ] setBytes updateBytes
DATE java.sql.Date setDate updateDate
TIME java.sql.Time setTime updateTime
TIMESTAMP java.sql.Timestamp setTimestamp updateTimestamp
CLOB java.sql.Clob setClob updateClob
BLOB java.sql.Blob setBlob updateBlob
ARRAY java.sql.Array setARRAY updateARRAY
REF java.sql.Ref SetRef updateRef
STRUCT java.sql.Struct SetStruct updateStruct

JDBC 3.0 has enhanced support for BLOB, CLOB, ARRAY, and REF data types. The
ResultSet object now has updateBLOB(), updateCLOB(), updateArray(), and
updateRef() methods that enable you to directly manipulate the respective data on the
server.

The setXXX() and updateXXX() methods enable you to convert specific Java types to
specific JDBC data types. The methods, setObject() and updateObject(), enable you to
map almost any Java type to a JDBC data type.

ResultSet object provides corresponding getXXX() method for each data type to
retrieve column value. Each method can be used with column name or by its ordinal
position.

SQL JDBC/Java setXXX getXXX

VARCHAR java.lang.String setString getString
CHAR java.lang.String setString getString
LONGVARCHAR java.lang.String setString getString
BIT boolean setBoolean getBoolean
NUMERIC java.math.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

Date & Time Data Types:

The java.sql.Date class maps to the SQL DATE type, and the java.sql.Time and
java.sql.Timestamp classes map to the SQL TIME and SQL TIMESTAMP data types,
respectively.

Following examples shows how the Date and Time classes format standard Java date
and time values to match the SQL data type requirements.

import java.sql.Date;
import java.sql.Time;
import java.sql.Timestamp;
import java.util.*;

public class SqlDateTime {

public static void main(String[] args) {
//Get standard date and time
java.util.Date javaDate = new java.util.Date();
long javaTime = javaDate.getTime();
System.out.println("The Java Date is:" +
javaDate.toString());

//Get and display SQL DATE

java.sql.Date sqlDate = new java.sql.Date(javaTime);
System.out.println("The SQL DATE is: " +
sqlDate.toString());

//Get and display SQL TIME

java.sql.Time sqlTime = new java.sql.Time(javaTime);
System.out.println("The SQL TIME is: " +
sqlTime.toString());
//Get and display SQL TIMESTAMP
java.sql.Timestamp sqlTimestamp =
new java.sql.Timestamp(javaTime);
System.out.println("The SQL TIMESTAMP is: " +
sqlTimestamp.toString());
}//end main
}//end SqlDateTime

Now let us compile above example as follows:

C:\>javac SqlDateTime.java
C:\>

When you run JDBCExample, it produces following result:

C:\>java SqlDateTime
The Java Date is:Tue Aug 18 13:46:02 GMT+04:00 2009
The SQL DATE is: 2009-08-18
The SQL TIME is: 13:46:02
The SQL TIMESTAMP is: 2009-08-18 13:46:02.828
C:\>

Handling NULL Values:

SQL's use of NULL values and Java's use of null are different concepts. So how do you
handle SQL NULL values in Java? There are three tactics you can use:

1. Avoid using getXXX( ) methods that return primitive data types.

2. Use wrapper classes for primitive data types, and use the ResultSet object's
wasNull( ) method to test whether the wrapper class variable that received the
value returned by the getXXX( ) method should be set to null.
3. Use primitive data types and the ResultSet object's wasNull( ) method to test
whether the primitive variable that received the value returned by the getXXX( )
method should be set to an acceptable value that you've chosen to represent a
NULL.

Here is one example to handle a NULL value:

Statement stmt = conn.createStatement( );

String sql = "SELECT id, first, last, age FROM Employees";
ResultSet rs = stmt.executeQuery(sql);

int id = rs.getInt(1);
if( rs.wasNull( ) ) {
id = 0;
}

JDBC - Transactions

If your JDBC Connection is in auto-commit mode, which it is by default, then every SQL
statement is committed to the database upon its completion.
That may be fine for simple applications, but there are three reasons why you may
want to turn off auto-commit and manage your own transactions:

1. To increase performance
2. To maintain the integrity of business processes
3. To use distributed transactions

Transactions enable you to control if, and when, changes are applied to the database.
It treats a single SQL statement or a group of SQL statements as one logical unit, and
if any statement fails, the whole transaction fails.

To enable manual- transaction support instead of the auto-commit mode that the JDBC
driver uses by default, use the Connection object's setAutoCommit() method. If you
pass a boolean false to setAutoCommit( ), you turn off auto-commit. You can pass a
boolean true to turn it back on again.

For example, if you have a Connection object named conn, code the following to turn
off auto-commit:

conn.setAutoCommit(false);

Commit & Rollback

Once you are done with your changes and you want to commit the changes then call
commit() method on connection object as follows:

conn.commit( );

Otherwise, to roll back updates to the database made using the Connection named
conn, use the following code:

conn.rollback( );

The following example illustrates the use of a commit and rollback object:

try{
//Assume a valid connection object conn
conn.setAutoCommit(false);
Statement stmt = conn.createStatement();

String SQL = "INSERT INTO Employees " +

"VALUES (106, 20, 'Rita', 'Tez')";
stmt.executeUpdate(SQL);
//Submit a malformed SQL statement that breaks
String SQL = "INSERTED IN Employees " +
"VALUES (107, 22, 'Sita', 'Singh')";
stmt.executeUpdate(SQL);
// If there is no error.
 conn.commit();
}catch(SQLException se){
// If there is any error.
conn.rollback();
}

In this case none of the abobe INSERT statement would success and everything would
be rolled back.

For a better understanding, I would suggest to study Commit - Example Code.

Using Savepoints:

The new JDBC 3.0 Savepoint interface gives you additional transactional control. Most
modern DBMS support savepoints within their environments such as Oracle's PL/SQL.

When you set a savepoint you define a logical rollback point within a transaction. If an
error occurs past a savepoint, you can use the rollback method to undo either all the
changes or only the changes made after the savepoint.

The Connection object has two new methods that help you manage savepoints:

1. setSavepoint(String savepointName): defines a new savepoint. It also

returns a Savepoint object.
2. releaseSavepoint(Savepoint savepointName): deletes a savepoint. Notice
that it requires a Savepoint object as a parameter. This object is usually a
savepoint generated by the setSavepoint() method.

There is one rollback ( String savepointName ) method which rolls back work to
the specified savepoint.

The following example illustrates the use of a Savepoint object:

try{
//Assume a valid connection object conn
conn.setAutoCommit(false);
Statement stmt = conn.createStatement();

//set a Savepoint
Savepoint savepoint1 = conn.setSavepoint("Savepoint1");
String SQL = "INSERT INTO Employees " +
"VALUES (106, 20, 'Rita', 'Tez')";
stmt.executeUpdate(SQL);
//Submit a malformed SQL statement that breaks
String SQL = "INSERTED IN Employees " +
"VALUES (107, 22, 'Sita', 'Tez')";
stmt.executeUpdate(SQL);
// If there is no error, commit the changes.
conn.commit();
}catch(SQLException se){
// If there is any error.
conn.rollback(savepoint1);
}

In this case none of the abobe INSERT statement would success and everything would
be rolled back.

JDBC - Exceptions Handling

Exception handling allows you to handle exceptional conditions such as program-

defined errors in a controlled fashion.

When an exception condition occurs, an exception is thrown. The term thrown means
that current program execution stops, and control is redirected to the nearest
applicable catch clause. If no applicable catch clause exists, then the program's
execution ends.

JDBC Exception handling is very similar to Java Excpetion handling but for JDBC, the
most common exception you'll deal with is java.sql.SQLException.

SQLException Methods:

A SQLException can occur both in the driver and the database. When such an
exception occurs, an object of type SQLException will be passed to the catch clause.

The passed SQLException object has the following methods available for retrieving
additional information about the exception:

Method Description
getErrorCode( ) Gets the error number associated with the
exception.
getMessage( ) Gets the JDBC driver's error message for an error
handled by the driver or gets the Oracle error
number and message for a database error.
getSQLState( ) Gets the XOPEN SQLstate string. For a JDBC
driver error, no useful information is returned
from this method. For a database error, the five-
digit XOPEN SQLstate code is returned. This
method can return null.
getNextException( ) Gets the next Exception object in the exception
chain.
printStackTrace( ) Prints the current exception, or throwable, and its
backtrace to a standard error stream.
printStackTrace(PrintStream s) Prints this throwable and its backtrace to the print
stream you specify.
printStackTrace(PrintWriter w) Prints this throwable and its backtrace to the print
writer you specify.

By utilizing the information available from the Exception object, you can catch an
exception and continue your program appropriately. Here is the general form of a try
block:

try {
// Your risky code goes between these curly braces!!!
}
catch(Exception ex) {
// Your exception handling code goes between these
// curly braces, similar to the exception clause
// in a PL/SQL block.
}
finally {
// Your must-always-be-executed code goes between these
// curly braces. Like closing database connection.
}

Example:

Study the following example code to understand the usage of try....catch...finally

blocks.

//STEP 1. Import required packages

import java.sql.*;

public class JDBCExample {

// JDBC driver name and database URL
static final String JDBC_DRIVER = "com.mysql.jdbc.Driver";
static final String DB_URL = "jdbc:mysql://localhost/EMP";

// Database credentials
static final String USER = "username";
static final String PASS = "password";

public static void main(String[] args) {

Connection conn = null;
try{
//STEP 2: Register JDBC driver
Class.forName("com.mysql.jdbc.Driver");

//STEP 3: Open a connection

System.out.println("Connecting to database...");
conn = DriverManager.getConnection(DB_URL,USER,PASS);
 //STEP 4: Execute a query
System.out.println("Creating statement...");
Statement stmt = conn.createStatement();
String sql;
sql = "SELECT id, first, last, age FROM Employees";
ResultSet rs = stmt.executeQuery(sql);

//STEP 5: Extract data from result set

while(rs.next()){
//Retrieve by column name
int id = rs.getInt("id");
int age = rs.getInt("age");
String first = rs.getString("first");
String last = rs.getString("last");

//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
}
//STEP 6: Clean-up environment
rs.close();
stmt.close();
conn.close();
}catch(SQLException se){
//Handle errors for JDBC
se.printStackTrace();
}catch(Exception e){
//Handle errors for Class.forName
e.printStackTrace();
}finally{
//finally block used to close resources
try{
if(conn!=null)
conn.close();
}catch(SQLException se){
se.printStackTrace();
}//end finally try
}//end try
System.out.println("Goodbye!");
}//end main
}//end JDBCExample

Now let us compile above example as follows:

C:\>javac JDBCExample.java
C:\>
When you run JDBCExample, it produces following result if there is no problem,
otherwise corresponding error would be caught and error message would be displayed:

C:\>java JDBCExample
Connecting to database...
Creating statement...
ID: 100, Age: 18, First: Zara, Last: Ali
ID: 101, Age: 25, First: Mahnaz, Last: Fatma
ID: 102, Age: 30, First: Zaid, Last: Khan
ID: 103, Age: 28, First: Sumit, Last: Mittal
C:\>

Try above example by passing wrong database name or wrong username or password
and check the result.

Batch Processing allows you to group related SQL statements into a batch and submit
them with one call to the database.

When you send several SQL statements to the database at once, you reduce the
amount of communication overhead, thereby improving performance.

JDBC drivers are not required to support this feature. You should use the
DatabaseMetaData.supportsBatchUpdates() method to determine if the target
database supports batch update processing. The method returns true if your
JDBC driver supports this feature.
The addBatch() method of Statement, PreparedStatement, and
CallableStatement is used to add individual statements to the batch. The
executeBatch() is used to start the execution of all the statements grouped
together.
The executeBatch() returns an array of integers, and each element of the array
represents the update count for the respective update statement.
Just as you can add statements to a batch for processing, you can remove them
with the clearBatch() method. This method removes all the statements you
added with the addBatch() method. However, you cannot selectively choose
which statement to remove.

Batching with Statement Object:

Here is a typical sequence of steps to use Batch Processing with Statment Object:

1. Create a Statement object using either createStatement() methods.

2. Set auto-commit to false using setAutoCommit().
3. Add as many as SQL statements you like into batch using addBatch() method on
created statement object.
4. Execute all the SQL statements using executeBatch() method on created
statement object.
5. Finally, commit all the changes using commit() method.
Example:

The following code snippet provides an example of a batch update using Statement
object:

// Create statement object

Statement stmt = conn.createStatement();

// Set auto-commit to false

conn.setAutoCommit(false);

// Create SQL statement

String SQL = "INSERT INTO Employees (id, first, last, age) " +
"VALUES(200,'Zia', 'Ali', 30)";
// Add above SQL statement in the batch.
stmt.addBatch(SQL);

// Create one more SQL statement

String SQL = "INSERT INTO Employees (id, first, last, age) " +
"VALUES(201,'Raj', 'Kumar', 35)";
// Add above SQL statement in the batch.
stmt.addBatch(SQL);

// Create one more SQL statement

String SQL = "UPDATE Employees SET age = 35 " +
"WHERE id = 100";
// Add above SQL statement in the batch.
stmt.addBatch(SQL);

// Create an int[] to hold returned values

int[] count = stmt.executeBatch();

//Explicitly commit statements to apply changes

conn.commit();

For a better understanding, I would suggest to study Batching - Example Code.

Batching with PrepareStatement Object:

Here is a typical sequence of steps to use Batch Processing with PrepareStatement

Object:

1. Create SQL statements with placeholders.

2. Create PrepareStatement object using either prepareStatement() methods.
3. Set auto-commit to false using setAutoCommit().
4. Add as many as SQL statements you like into batch using addBatch() method on
created statement object.
5. Execute all the SQL statements using executeBatch() method on created
statement object.
6. Finally, commit all the changes using commit() method.
The following code snippet provides an example of a batch update using
PrepareStatement object:

// Create SQL statement

String SQL = "INSERT INTO Employees (id, first, last, age) " +
"VALUES(?, ?, ?, ?)";

// Create PrepareStatement object

PreparedStatemen pstmt = conn.prepareStatement(SQL);

//Set auto-commit to false

conn.setAutoCommit(false);

// Set the variables

pstmt.setInt( 1, 400 );
pstmt.setString( 2, "Pappu" );
pstmt.setString( 3, "Singh" );
pstmt.setInt( 4, 33 );
// Add it to the batch
pstmt.addBatch();

// Set the variables

pstmt.setInt( 1, 401 );
pstmt.setString( 2, "Pawan" );
pstmt.setString( 3, "Singh" );
pstmt.setInt( 4, 31 );
// Add it to the batch
pstmt.addBatch();

//add more batches

.
.
.
.
//Create an int[] to hold returned values
int[] count = stmt.executeBatch();

//Explicitly commit statements to apply changes

conn.commit();

JDBC - Stored Procedures

I have explained how to use Stored Procedures in JDBC while discussing JDBC -
Statements. This tutorial is similar to that section but it would give you additional
information about JDBC SQL escape syntax.

Just as a Connection object creates the Statement and PreparedStatement objects, it

also creates the CallableStatement object which would be used to execute a call to a
database stored procedure.
Creating CallableStatement Object:

Suppose, you need to execute the following Oracle stored procedure:

CREATE OR REPLACE PROCEDURE getEmpName

(EMP_ID IN NUMBER, EMP_FIRST OUT VARCHAR) AS
BEGIN
SELECT first INTO EMP_FIRST
FROM Employees
WHERE ID = EMP_ID;
END;

NOTE: Above stored procedure has been written for Oracle, but we are working with
MySQL database so let us write same stored procedure for MySQL as follows to create
it in EMP database:

DELIMITER $$

DROP PROCEDURE IF EXISTS `EMP`.`getEmpName` $$

CREATE PROCEDURE `EMP`.`getEmpName`
(IN EMP_ID INT, OUT EMP_FIRST VARCHAR(255))
BEGIN
SELECT first INTO EMP_FIRST
FROM Employees
WHERE ID = EMP_ID;
END $$

DELIMITER ;

Three types of parameters exist: IN, OUT, and INOUT. The PreparedStatement object
only uses the IN parameter. The CallableStatement object can use all three.

Here are the definitions of each:

Parameter Description
IN A parameter whose value is unknown when the SQL
statement is created. You bind values to IN parameters with
the setXXX() methods.
OUT A parameter whose value is supplied by the SQL statement it
returns. You retrieve values from theOUT parameters with the
getXXX() methods.
INOUT A parameter that provides both input and output values. You
bind variables with the setXXX() methods and retrieve values
with the getXXX() methods.
The following code snippet shows how to employ the Connection.prepareCall()
method to instantiate a CallableStatement object based on the preceding stored
procedure:

CallableStatement cstmt = null;

try {
String SQL = "{call getEmpName (?, ?)}";
cstmt = conn.prepareCall (SQL);
. . .
}
catch (SQLException e) {
. . .
}
finally {
. . .
}

The String variable SQL represents the stored procedure, with parameter placeholders.

Using CallableStatement objects is much like using PreparedStatement objects. You

must bind values to all parameters before executing the statement, or you will receive
an SQLException.

If you have IN parameters, just follow the same rules and techniques that apply to a
PreparedStatement object; use the setXXX() method that corresponds to the Java data
type you are binding.

When you use OUT and INOUT parameters you must employ an additional
CallableStatement method, registerOutParameter(). The registerOutParameter()
method binds the JDBC data type to the data type the stored procedure is expected to
return.

Once you call your stored procedure, you retrieve the value from the OUT parameter
with the appropriate getXXX() method. This method casts the retrieved value of SQL
type to a Java data type.

Closing CallableStatement Obeject:

Just as you close other Statement object, for the same reason you should also close
the CallableStatement object.

A simple call to the close() method will do the job. If you close the Connection object
first it will close the CallableStatement object as well. However, you should always
explicitly close the CallableStatement object to ensure proper cleanup.

CallableStatement cstmt = null;

try {
String SQL = "{call getEmpName (?, ?)}";
cstmt = conn.prepareCall (SQL);
 . . .
}
catch (SQLException e) {
. . .
}
finally {
cstmt.close();
}

For a better understanding, I would suggest to study Callable - Example Code.

JDBC SQL escape syntax:

The escape syntax gives you the flexibility to use database specific features unavailable
to you by using standard JDBC methods and properties.

The general SQL escape syntax format is as follows:

{keyword 'parameters'}

Here are following escape sequences which you would find very useful while doing
JDBC programming:

d, t, ts Keywords:

They help identify date, time, and timestamp literals. As you know, no two DBMSs
represent time and date the same way. This escape syntax tells the driver to render
the date or time in the target database's format. For Example:

{d 'yyyy-mm-dd'}

Where yyyy = year, mm = month; dd = date. Using this syntax {d '2009-09-03'} is

March 9, 2009.

Here is a simple example showing how to INSERT date in a table:

//Create a Statement object

stmt = conn.createStatement();
//Insert data ==> ID, First Name, Last Name, DOB
String sql="INSERT INTO STUDENTS VALUES" +
"(100,'Zara','Ali', {d '2001-12-16'})";

stmt.executeUpdate(sql);

Similarly, you can use one of the following two syntaxes, either t or ts:

{t 'hh:mm:ss'}
Where hh = hour; mm = minute; ss = second. Using this syntax {t '13:30:29'} is
1:30:29 PM.

{ts 'yyyy-mm-dd hh:mm:ss'}

This is combined syntax of the above two syntax for 'd' and 't' to represent timestamp.

escape Keyword:

This keyword identifies the escape character used in LIKE clauses. Useful when using
the SQL wildcard %, which matches zero or more characters. For example:

String sql = "SELECT symbol FROM MathSymbols

WHERE symbol LIKE '\%' {escape '\'}";
stmt.execute(sql);

If you use the backslash character (\) as the escape character, you also have to use
two backslash characters in your Java String literal, because the backslash is also a
Java escape character.

fn Keyword:

This keyword represents scalar functions used in a DBMS. For example, you can use
SQL function length to ge the length of a string:

{fn length('Hello World')}

This returns 11, the length of the character string 'Hello World'.

call Keyword:

This keywork is used to call stored procedures. For example, for a stored procedure
requiring an IN parameter, use following syntax:

{call my_procedure(?)};

For a stored procedure requiring an IN parameter and returning an OUT parameter,

use following syntax:

{? = call my_procedure(?)};

oj Keyword:

This keyword is used to signify outer joins. The syntax is as follows:

{oj outer-join}
Where outer-join = table {LEFT|RIGHT|FULL} OUTERJOIN {table | outer-join} on
search-condition. For example:

String sql = "SELECT Employees

FROM {oj ThisTable RIGHT
OUTER JOIN ThatTable on id = '100'}";
stmt.execute(sql);

JDBC - Streaming Data

A PreparedStatement object has the ability to use input and output streams to supply
parameter data. This enables you to place entire files into database columns that can
hold large values, such as CLOB and BLOB data types.

There are following methods which can be used to stream data:

1. setAsciiStream(): This method is used to supply large ASCII values.

2. setCharacterStream(): This method is used to supply large UNICODE values.
3. setBinaryStream(): This method is used to supply large binary values.

The setXXXStream() method requires an extra parameter, the file size, besides the
parameter placeholder. This parameter informs the driver how much data should be
sent to the database using the stream.

Example

Consider we want to upload an XML file XML_Data.xml into a database table. Here is
the content of this XML file:

<?xml version="1.0"?>
<Employee>
<id>100</id>
<first>Zara</first>
<last>Ali</last>
<Salary>10000</Salary>
<Dob>18-08-1978</Dob>
<Employee>

Keep this XML file in the same directory where you are going to run this example.

This example would create a database table XML_Data and then file XML_Data.xml
would be uploaded into this table.

Copy and past following example in JDBCExample.java, compile and run as follows:

// Import required packages

import java.sql.*;
import java.io.*;
import java.util.*;

public class JDBCExample {

// JDBC driver name and database URL
static final String JDBC_DRIVER = "com.mysql.jdbc.Driver";
static final String DB_URL = "jdbc:mysql://localhost/EMP";

// Database credentials
static final String USER = "username";
static final String PASS = "password";

public static void main(String[] args) {

Connection conn = null;
PreparedStatement pstmt = null;
Statement stmt = null;
ResultSet rs = null;
try{
// Register JDBC driver
Class.forName("com.mysql.jdbc.Driver");

// Open a connection
System.out.println("Connecting to database...");
conn = DriverManager.getConnection(DB_URL,USER,PASS);

//Create a Statement object and build table

stmt = conn.createStatement();
createXMLTable(stmt);

//Open a FileInputStream
File f = new File("XML_Data.xml");
long fileLength = f.length();
FileInputStream fis = new FileInputStream(f);

//Create PreparedStatement and stream data

String SQL = "INSERT INTO XML_Data VALUES (?,?)";
pstmt = conn.prepareStatement(SQL);
pstmt.setInt(1,100);
pstmt.setAsciiStream(2,fis,(int)fileLength);
pstmt.execute();

//Close input stream

fis.close();

// Do a query to get the row

SQL = "SELECT Data FROM XML_Data WHERE id=100";
rs = stmt.executeQuery (SQL);
// Get the first row
if (rs.next ()){
//Retrieve data from input stream
InputStream xmlInputStream = rs.getAsciiStream (1);
int c;
 ByteArrayOutputStream bos = new ByteArrayOutputStream();
while (( c = xmlInputStream.read ()) != -1)
bos.write(c);
//Print results
System.out.println(bos.toString());
}
// Clean-up environment
rs.close();
stmt.close();
pstmt.close();
conn.close();
}catch(SQLException se){
//Handle errors for JDBC
se.printStackTrace();
}catch(Exception e){
//Handle errors for Class.forName
e.printStackTrace();
}finally{
//finally block used to close resources
try{
if(stmt!=null)
stmt.close();
}catch(SQLException se2){
}// nothing we can do
try{
if(pstmt!=null)
pstmt.close();
}catch(SQLException se2){
}// nothing we can do
try{
if(conn!=null)
conn.close();
}catch(SQLException se){
se.printStackTrace();
}//end finally try
}//end try
System.out.println("Goodbye!");
}//end main

public static void createXMLTable(Statement stmt)

throws SQLException{
System.out.println("Creating XML_Data table..." );
//Create SQL Statement
String streamingDataSql = "CREATE TABLE XML_Data " +
"(id INTEGER, Data LONG)";
//Drop table first if it exists.
try{
stmt.executeUpdate("DROP TABLE XML_Data");
}catch(SQLException se){
}// do nothing
//Build table.
 stmt.executeUpdate(streamingDataSql);
}//end createXMLTable
}//end JDBCExample

Now let us compile above example as follows:

C:\>javac JDBCExample.java
C:\>

When you run JDBCExample, it produces following result:

C:\>java JDBCExample
Connecting to database...
Creating XML_Data table...
<?xml version="1.0"?>
<Employee>
<id>100</id>
<first>Zara</first>
<last>Ali</last>
<Salary>10000</Salary>
<Dob>18-08-1978</Dob>
<Employee>
Goodbye!
C:\>