What is JDBC?

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 or MySQL statements
• Executing that SQL or MySQL queries in the database
• Viewing & Modifying the resulting records

Fundamentally, JDBC is a specification that provides a complete set of interfaces that allows for
portable access to an underlying database. Java can be used to write different types of
executables, such as:

• Java Applications
• Java Applets
• Java Servlets
• Java ServerPages (JSPs)
• Enterprise JavaBeans (EJBs)

All of these different executables are able to use a JDBC driver to access a database and take
advantage of the stored data.

JDBC provides the same capabilities as ODBC, allowing Java programs to contain database-
independent code.

Pre-Requisite:
Before progressing on this tutorial you need to have good understanding on the following two
subjects:

1. Core JAVA Programming

2. SQL or MySQL Database

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.

The JDBC API uses a driver manager and database-specific drivers to provide transparent
connectivity to heterogeneous databases.

The JDBC driver manager ensures that the correct driver is used to access each data source. The
driver manager is capable of supporting multiple concurrent drivers connected to multiple
heterogeneous databases.

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 interface 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 the communications with the database server. You will
interact directly with Driver objects very rarely. Instead, you use DriverManager objects,
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 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 enable 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 Drivers 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 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 accessing databases. The JDBC clients
use standard network sockets to communicate with an 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 a 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.

fter 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 the 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
jdbc:oracle:thin:@hostname:port
ORACLE oracle.jdbc.driver.OracleDriver
Number:databaseName
DB2 COM.ibm.db2.jdbc.net.DB2Driver jdbc:db2:hostname:port Number/databaseName
jdbc:sybase:Tds:hostname: port
Sybase com.sybase.jdbc.SybDriver
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();

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

Use for general-purpose access to your database. Useful when you are
Statement using static SQL statements at runtime. The Statement interface
cannot accept parameters.
Use when you plan to use the SQL statements many times. The
PreparedStatement
PreparedStatement interface accepts input parameters at runtime.
Use when you want to access database stored procedures. The
CallableStatement
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
A parameter whose value is unknown when the SQL statement is
IN created. You bind values to IN parameters with the setXXX()
methods.
A parameter whose value is supplied by the SQL statement it returns.
OUT You retrieve values from theOUT parameters with the getXXX()
methods.
A parameter that provides both input and output values. You bind
INOUT 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.
The cursor can scroll forwards and backwards, and
the result set is not sensitive to changes made by
ResultSet.TYPE_SCROLL_INSENSITIVE
others to the database that occur after the result set
was created.
The cursor can scroll forwards and backwards, and
the result set is sensitive to changes made by others
ResultSet.TYPE_SCROLL_SENSITIVE.
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

 public void beforeFirst() throws SQLException
1
Moves the cursor to just before the first row
public void afterLast() throws SQLException
2
Moves the cursor to just after the last row
public boolean first() throws SQLException
3
Moves the cursor to the first row
public void last() throws SQLException
4
Moves the cursor to the last row.
public boolean absolute(int row) throws SQLException
5
Moves the cursor to the specified row
public boolean relative(int row) throws SQLException
6 Moves the cursor the given number of rows forward or backwards from where it currently
is pointing.
public boolean previous() throws SQLException
7 Moves the cursor to the previous row. This method returns false if the previous row is off
the result set
public boolean next() throws SQLException
8 Moves the cursor to the next row. This method returns false if there are no more rows in the
result set
public int getRow() throws SQLException
9
Returns the row number that the cursor is pointing to.
public void moveToInsertRow() throws SQLException
10 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.
public void moveToCurrentRow() throws SQLException
11 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

public int getInt(String columnName) throws SQLException
1
Returns the int in the current row in the column named columnName
public int getInt(int columnIndex) throws SQLException
2 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

public void updateString(int columnIndex, String s) throws SQLException
1
Changes the String in the specified column to the value of s.
public void updateString(String columnName, String s) throws SQLException
2 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

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

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

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
java.sql.ResultSet interface
A positioned update or delete issued against a cursor being accessed through a ResultSet object
modifies or deletes the current row of the ResultSet object.

Some intermediate protocols might pre-fetch rows. This causes positioned updates and deletes to
operate against the row the underlying cursor is on, and not the current row of the ResultSet.

JDBC does not define the sort of rounding to use for ResultSet.getBigDecimal. Derby uses
java.math.BigDecimal.ROUND_HALF_DOWN.

Table 1. Implementation Notes on ResultSet Methods

Returns Signature Implementation Notes
void deleteRow() After the row is deleted, the ResultSet object will
be positioned before the next row. Before issuing
any methods other than close on the ResultSet
object, the program will need to reposition the
ResultSet object.
int getConcurrency() If the Statement object has
CONCUR_READ_ONLY concurrency, then this
method will return
ResultSet.CONCUR_READ_ONLY. But if the
Statement object has CONCUR_UPDATABLE
concurrency, then the return value will depend on
whether the underlying language ResultSet is
updatable or not. If the language ResultSet is
updatable, then getConcurrency() will return
ResultSet.CONCUR_UPDATABLE. If the
language ResultSet is not updatable, then
getConcurrency() will return
ResultSet.CONCUR_READ_ONLY.
boolean rowDeleted() For forward-only result sets this method always
returns false, for scrollable result sets it returns
true if the row has been deleted, via result set or
positioned delete.
boolean rowInserted() Always returns false.
boolean rowUpdated() For forward-only result sets this method always
returns false, for scrollable result sets it returns
true if the row has been updated, via result set or
positioned update.
 Table 1. Implementation Notes on ResultSet Methods
Returns Signature Implementation Notes
void updateRow() After the row is updated, the ResultSet object
will be positioned before the next row. Before
issuing any methods other than close on the
ResultSet object, the program will need to
reposition the ResultSet object.