JDBC Programming

JDBC
2015 NetCracker Technology Corporation Confidential
Course Objectives
By the end of this course, you will be able to:
Understand the database connectivity from a Java Program
Understand to execute different types of SQL and PL/SQL
query from Java
Course Contents
1.
JDBC Overview
2.
JDBC Architecture
3.
JDBC API
4.
JDBC Driver
5.
Building Connection and Execute Query
6.
ResultSet
Course Contents
7.
Calling PL/SQL
8.
Batch Update
9.
JDBC Transaction
Introduction
Overview
Call-level interfaces such as JDBC are programming interfaces allowing external
access to SQL database manipulation and update commands.
They allow the integration of SQL calls into a general programming environment
by providing library routines, which interface with the database.
In particular, Java based JDBC has a rich collection of routines which make such an
interface extremely simple and intuitive.
Overview
Here is an easy way of visualizing what happens in a call level interface:
You are writing a normal Java program. Somewhere in the program, you need to
interact with a database. Using standard library routines, you open a connection
to the database. You then use JDBC to send your SQL code to the database, and
process the results that are returned. When you are done, you close the
connection.
Standard
Standard
Sub-Routine
Sub-Routine
send SQL code

The connection pipe
retrieve the rows
Database
Do not forget
to close the
connection when
you are
DONE !!!
Why Do We Need JDBC?

A Question to you all.
Why can't application developers use ODBC (Open Database Connectivity) on the
Java platform? After all, it's an established standard API for database access.
You can use ODBC; however, ODBC isn't appropriate for direct use from the Java
programming language because it uses a C interface.
The JDBC API was modeled after ODBC, but, because JDBC is a Java API, it offers a
natural Java interface for working with SQL.
JDBC is needed to provide a Pure Java" solution for application development.
JDBC
Architecture
JDBC is Sun's attempt to create a platform-neutral interface between databases

and Java.
With JDBC, you can count on a standard set of database access features and
(usually) a particular subset of SQL.
The JDBC API defines a set of interfaces that encapsulate major database
functionality, including running queries, processing results, and determining
configuration information.
A database vendor or third-party developer writes a JDBC driver, which is a set of
classes that implements these interfaces for a particular database system. An
application can use a number of drivers interchangeably.
Figure in the next slide shows how an application uses JDBC to interact with one or
more databases without knowing about the underlying driver implementations.
JDBC Architecture
Type 1
Type 1
Type 2
Type 2
Type 3
Type 3
Type 4
Type 4
We will
discuss on type
of database
driver later on
10
What We Need?
Install Java on your machine
Install a driver on your machine
Install your DBMS if needed

Database
Database
11
JDBC API
12
JDBC API
What is an API?
Abbreviation of Application Program Interface, a set of routines and tools for
building software applications.
A good API makes it easier to develop a program by providing all the building
blocks.
A programmer puts the blocks together.
In Java also, we have a set of useful classes and interfaces to implement the
concept of JDBC.
These classes and methods in turn provides number of useful methods to perform
several tasks.
The whole JDBC API is present under java.sql package.
To use them we will use the statement: import java.sql.*;
13
JDBC API
This is not the

complete list but
the list of most
frequently used
classes and
interfaces
14
DriverManager
This is a very important class.
Its main purpose is to provide a means of managing the different types of JDBC
database driver On running an application, it is the DriverManager's responsibility
to load all the drivers found in the system property jdbc drivers.
For example, this is where the driver for the Oracle database may be defined. This
is not to say that a new driver cannot be explicitly stated in a program at runtime,
which is not included in jdbc drivers.
When opening a connection to a database it is the DriverManager' s role to choose
the most appropriate driver from the previously loaded drivers.
15
Connection
When a connection is opened, this represents a single instance of a particular

database session. As long as the connection remains open, SQL queries may be
executed and results obtained.
This interface can be used to retrieve information regarding the table

descriptions, and any other information about the database to which you are
connected.
By using Connection a commit is automatic after the execution of a successful

SQL statement, unless auto commit has been explicitly disabled.
In this case a commit command must follow each SQL statement otherwise
changes will not be saved. An unnatural disconnection from the database during
an SQL statement will automatically result in the rollback of that query, and
everything else back to the last successful commit.
16
Statement
The objective of the Statement interface is to pass the SQL statement as a string to
the database for execution and to retrieve any results from the database in the
form of a ResultSet.
Only one ResultSet can be open per statement at any single point of time.
For example, two ResultSets cannot be compared to each other if both ResultSets
stemmed from the same SQL statement.
If an SQL statement is re-issued for any reason, the old Resultset will automatically
get closed.
SQL statement as string

Database
Database
ResultSet
17
PreparedStatement
A PreparedStatement object is an SQL statement, which is pre-compiled and
stored.
This object can then be executed multiple times much more efficiently than
preparing and issuing the same statement each time it is needed.
When defining a variable type in JDBC, the program must ensure that the type
corresponds with the database field type for IN and OUT parameters.
Insert Into emp(empno,ename,job,deptno) Values(?,?,?,?)

Update emp set sal=sal+100 Where deptno=?
We will have
a detail discussion
on this later on.
18
CallableStatement
This interface is used to execute previously stored SQL procedures
Consider this: SELECT cname FROM tname WHERE cname = var;
If this statement were to be stored, the program would need a way to pass the
parameter var into the callable procedure.
Parameters passed into the call are referred to sequentially, by number.
When defining a variable type in JDBC the program must ensure that the type
corresponds with the database field type for IN and OUT parameters
Database
Java Application
Call to procedure
procedure
table
Return value
through its
OUT parameter
19
ResultSet
A ResultSet is the retrieved data from a currently executed SQL statement. The
data from the query is delivered in the form of a table.
A pointer known as a cursor holds the current retrieved record. When a ResultSet
is returned, the logical pointer is positioned before the first record.
The pointer can move in a top-down approach (by default). Special parameters
needs to be set in order to make the pointer move in backward direction.
Once the last row has been retrieved the statement is considered closed, and
this causes the ResultSet to be automatically closed.
Row for the column heading
SQL query
ResultSet
Database
Database
e
Th
et
S
t
ul
s
Re
Rows
Initially the pointer will

be placed just before
the 1st st available row.
20
MetaData
What Is Metadata?
Metadata is a component of data which describes the data.
It is "data about data."
ResultSetMetaData
This interface allows a program to determine types and properties in any columns
in a ResultSet. It may be used to find out a data type for a particular field before
assigning its variable type.
DatabaseMetaData
This interface supplies information about the database as a whole. MetaData
refers to information held about data. The information returned is in the form of
ResultSet. Normal ResultSet methods, as explained previously, may be used in this
instance. If metadata is not available for the particular request then an
SQLException will occur
21
Driver
What Is Database Driver?
A database driver is nothing but a component which helps the application to get
access over a database.
Driver
For each database driver a class that implements the Driver interface must be
provided. When such a class is loaded it should register itself with the
DriverManager, which will then allow it to be accessed by a program.
We will have
a detail discussion
on Driver later on.
22
JDBC Driver, Making Connection & Execute Query
23
JDBC Driver Type 1
Type 1 : JDBC-ODBC bridge drivers
Advantage
Advantage
* The JDBC-ODBC Bridge allows access to almost any

database, since the database's ODBC drivers are already
available.
Disadvantages
Disadvantages
* Since the Bridge driver is not written fully in Java, Type 1
drivers are not portable.
* A performance issue is seen as a JDBC call goes through
the bridge to the ODBC driver, then to the database, and
this applies even in the reverse process. They are the slowest
of all driver types.
* The client system requires the ODBC Installation to use
the driver.
* Not good for the Web.
24
JDBC Driver Type 2
Type 2 : Native-API partly Java drivers
Advantage
Advantage
* Type 2 drivers typically offer better performance than

the JDBC-ODBC Bridge as the layers of communication
(tiers) are less than that of Type 1 and also it uses Native API
which is Database specific.
Disadvantages
Disadvantages
* Native API must be installed in the Client System and
hence type 2 drivers cannot be used for the Internet.
* Like Type 1 drivers, its not written in Java Language
which forms a portability issue.
* If we change the Database we have to change the native
API as it is specific to a database.
* Mostly obsolete now.
* Usually not thread safe.
25
JDBC Driver Type 3
Type 3 : Net-protocol All-Java drivers
Advantages
Advantages
* This driver is server-based, so there is no need for any
vendor database library to be present on client machines.
* This driver is fully written in Java and hence Portable. It is
suitable for the web.
* There are many opportunities to optimize portability,
performance, and scalability.
* The net protocol can be designed to make the client JDBC
driver very small and fast to load.
* The type 3 driver typically provides support for features
such as caching (connections, query results, and so on),
load balancing, and advanced system administration such as
logging and auditing.
* This driver is very flexible allows access to multiple
databases using one driver.
* They are the most efficient amongst all driver types.
Disadvantages
Disadvantages
* It requires another server application to install and
maintain. Traversing the resultset may take longer, since the
data comes through the backend server.
26
JDBC Driver Type 4
Type 4 : Native-protocol All-Java drivers
Advantages
Advantages
* Type 4 drivers are completely written in Java to achieve

platform independence and eliminate deployment
administration issues. It is most suitable for the web.
* Number of translation layers is very less i.e. type 4 JDBC

drivers don't have to translate database requests to ODBC
or a native connectivity interface or to pass the request on
to another server, performance is typically quite good.
* You dont need to install special software on the client or
server. Further, these drivers can be downloaded
dynamically.
Disadvantages
Disadvantages
* With type 4 drivers, the user needs a different driver for
each database.
A list of currently available JDBC drivers is available at - http://java.sun.com/products/jdbc/jdbc.drivers.html
27
JDBC Drivers At a glance

Driver Type 1
Driver Type 1
JDBC-ODBC bridge drivers

JDBC-ODBC bridge drivers
This driver type is the JDBC-ODBC bridge

It is limited to running locally
Must have ODBC installed on computer
Must have ODBC driver for specific database installed on computer
Generally cant run inside an applet because of Native Method calls
Driver Type 2
Driver Type 2
Native-API partly Java drivers

Native-API partly Java drivers
Native Database library driver

Uses Native Database library on computer to access database
Generally cant run inside an applet because of Native Method calls
Must have database library installed on client
28
JDBC Drivers At a glance

Driver Type 3
Driver Type 3
Net-protocol All-Java drivers

Net-protocol All-Java drivers
100% Java Driver, NO native methods

Does NOT require pre-installation on client
Can be downloaded and configured on-the-fly just like any Java class file
Uses a proprietary protocol for talking with a middleware server
Middleware server converts from proprietary calls to DBMS specific calls
Driver Type 4
Driver Type 4
Native-protocol All-Java drivers

Native-protocol All-Java drivers
100% Java Driver, NO native methods

Does NOT require pre-installation on client
Can be downloaded and configured on-the-fly just like any Java class file
Unlike Type III driver, talks DIRECTLY with DBMS Server
Converts JDBC calls directly to database specific calls
29
A JDBC Code to test a connection

Step 1
Load
Loadthe
thedriver
driver
Using
Usingthe
theJDBC-ODBC
JDBC-ODBCBridge
Bridgedriver
driver(Type
(Type1)1)
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Using
Usingthe
theOracle
Oraclethin
thindriver
driver(Type
(Type4)4)
Class.forName("oracle.jdbc.driver.OracleDriver");
Established
Establishedthe
theconnection
connection
Step 2
IfIfType
Type11driver
driverhas
hasbeen
beenused
usedthen
thendo
dothe
thefollowing:
following:
Connection
Connectionc=DriverManager.getConnection("jdbc:odbc:dsn",
c=DriverManager.getConnection("jdbc:odbc:dsn","scott",
"scott","tiger");
"tiger");
If Type 4 driver has been used then do the following:
If Type 4 driver has been used then do the following:
Connection c=DriverManager.getConnection("jdbc:oracle:thin:@9iserver:1521:or", "scott", "tiger");
Connection c=DriverManager.getConnection("jdbc:oracle:thin:@9iserver:1521:or", "scott", "tiger");
30
database
database
import java.sql.*;
public class TestConnection
{
public static void main (String args[])
{
try
{
Connection conn;
conn=DriverManager.getConnection("jdbc:oracle:thin:@oraserver:1521:or", "scott",
"tiger");
// oraserver is the name of the oracle database machine
// or is the name of the host string
System.out.println(Connection Established!!!!!);
}
catch(Exception e) {System.out.println(e.toString());}
}
}
database
The Complete Program - Building the connection
31
Time has come to use the connection
Now after making the connection its the time to perform certain tasks
(Select/Insert/Update/Delete) on a table. Following are the steps you need to go by:
Step 3
Create
CreateaaStatement
Statementobject
objectusing
usingthe
theavailable
availableConnection
Connectionobject
object
Statement
Statementstmt=conn.createStatement();
stmt=conn.createStatement();
Here
Herestmt
stmtcan
canbe
bethought
thoughtofofasasan
anagent
agenttotohold/carry
hold/carryan
anSQL
SQLstatement.
statement.
Execute
ExecuteaaSelect
Selectquery
queryand
andhold
holdthe
thefetched
fetchedrows
rowsininaaResultSet
ResultSetobject
object
Step 4
ResultSet
ResultSetrs=stmt.executeQuery("select
rs=stmt.executeQuery("selectename,sal
ename,salfrom
fromemp");
emp");
The
logical
record
pointer
will
always
be
there
before
the
first
available
The logical record pointer will always be there before the first availablerow.
row.
Step 5
Now
Nowiterate
iteratethrough
throughaaloop
looptotoextract
extractand
andprint
printthe
thevalues
values
while
while(rs.next())
(rs.next())
{{
System.out.print(rs.getString(1)+"
System.out.print(rs.getString(1)+" ");
");
System.out.println(rs.getFloat(2)+"
System.out.println(rs.getFloat(2)+" ");
");
}}
1 here means the 1st available

column within the ResultSet.
Instead of specifying the
column number, column name
can also be specified.
32
The Complete Program - Fetching rows from table
Using Statement
import java.sql.*;
public class TestConnection{
public static void main (String args[]){
try{
Connection conn; Statement stmt; ResultSet rs;
"tiger");
System.out.println(Connection Established!!!!!);
stmt=conn.createStatement();
// the method executeQuery needs to be invoked only for a Select Query.
// Later on we will see the use of executeUpdate for Insert/Update/Delete etc.
rs=stmt.executeQuery("select ename,sal from emp");
while (rs.next()){
System.out.print(rs.getString(1)+" ");
System.out.println(rs.getFloat(2)+"
");
}
}
}
}
33
The Complete Program - Fetching rows from table
Using PreparedStatement
import java.sql.*;
public class TestConnection
{
public static void main (String args[])
{
try{
Connection conn; PreparedStatement pstmt; ResultSet rs;
"tiger");
pstmt=conn.prepareStatement("select ename,sal from emp");
rs=pstmt.executeQuery();
while (rs.next())
{
System.out.print(rs.getString(1)+" ");System.out.println(rs.getFloat(2)+"
");
}
}
}
}
34
Statement Vs. PreparedStatement

2
3
4
Parse
Parsethe
theincoming
incomingSQL
SQLquery
query
Compile
Compilethe
theSQL
SQLquery
query
Plan/optimize
Plan/optimizethe
thedata
dataacquisition
acquisitionpath
path
Execute
Executethe
theoptimized
optimizedquery
queryand
andreturn
returndata
data
Prepared
Statement
Statement
Most relational databases handles a JDBC / SQL query in four steps:
A Statement will always proceed through the four steps above for each SQL query sent
to the database. A PreparedStatement pre-executes steps 1 to 3 in the execution
process above. Thus, when creating a PreparedStatement some pre-optimization is
performed immediately. The effect is to lessen the load on the database engine at
execution time.
Another advantage of the PreparedStatement class is the ability to create an incomplete
query and supply parameter values at execution time. This type of query is well suited
for filtering queries which may differ in parameter value only.
35
ResultSet
36
Handling ResultSets in JDBC

Row for the column heading
SQL query
ResultSet
Database
Database
e
Th
et
S
t
ul
s
Re
Rows
Initially the pointer will

be placed just before
the 1st st available row.
This ResultSet can be resulted with the invocation of executeQuery() method of

Statement or PreparedStatement.
The prepareCall() method of CallableStatement can also return a ResultSet
Limitations
In JDBC 1.0, the resultsets so defined were limited in scope in that the rows in the resultset
could be accessed only in the forward-direction. This means there was no way of moving
back and forth in a resultset or jumping to a particular row identified by a row number.
Also, the resultsets were read-only in that there was no way for inserting new rows into
the resultset, updating a particular row, or deleting a particular row.
37
Navigating through the ResultSet
By default the logical record pointer can only move in a top-to-bottom approach.
So, in case we want to move in a upward direction through the ResultSet we need
to do something extra.
We need to invoke the createStatement method with the following two
arguments:
1st
1stargument
argument(resultSetType)
(resultSetType)
2nd
2ndargument
argument(resultSetConcurrency
(resultSetConcurrency) )
Initially the pointer

will be placed just
before the 1st st
available row.
e
Th
et
tl S
su
e
R
ResultSet.TYPE_SCROLL_INSENSITIVE
ResultSet.CONCUR_READ_ONLY
Row for the column
heading
Rows
With
PreparedStatement, this
is not possible
Bi-directional
movement
38
Navigating
through
the
ResultSet
import java.sql.*;import java.awt.*;import java.awt.event.*;
DataNavigator.j
ava
public class DataNavigator{public static void main(String args[]){TheFrame f=new TheFrame();}}

class TheFrame extends Frame implements ActionListener
{
Connection conn;Statement stmt;ResultSet rs;Label l1,l2,l3,l4;TextField t1,t2,t3,t4; Button b1,b2,b3,b4;Panel
p1,p2,p3,p4,p5;
public TheFrame()
{ super();
l1=new Label("Empno :"); l2=new Label("Name :");l3=new Label("Job :"); l4=new Label("Sal :");
t1=new TextField(4); t2=new TextField(9); t3=new TextField(10); t4=new TextField(4);
b1=new Button("First"); b2=new Button("Last "); b3=new Button("Next "); b4=new Button("Prev ");
b1.addActionListener(this);b2.addActionListener(this);b3.addActionListener(this);b4.addActionListener(this);
p1=new Panel();p2=new Panel();p3=new Panel();p4=new Panel();p5=new Panel();
p1.add(l1); p1.add(t1); p2.add(l2); p2.add(t2); p3.add(l3); p3.add(t3); p4.add(l4); p4.add(t4);
p5.add(b1);p5.add(b2);p5.add(b3);p5.add(b4); setLayout(new GridLayout(5,1));
add(p1);add(p2);add(p3);add(p4);add(p5);
try{
conn=DriverManager.getConnection("jdbc:odbc:oradsn","scott","tiger");
stmt=conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ_ONLY);
rs=stmt.executeQuery("Select * from emp"); rs.next();
}
catch(Exception e){System.out.println(e.toString());}
displayValues();setSize(300,300); setVisible(true);
}
Continued
..
39
Remaining
part
of
the
Navigator
public void actionPerformed(ActionEvent ae)
{
if(ae.getSource().equals(b1)){
try{rs.first();}catch(Exception e){System.out.println(e.toString());} displayValues();
}
if(ae.getSource().equals(b2)) {
try{rs.last();}catch(Exception e){System.out.println(e.toString());} displayValues();
}
try{rs.next();}catch(Exception e){System.out.println(e.toString());} displayValues();
}
try{rs.previous();}catch(Exception e){System.out.println(e.toString());} displayValues()
}
}
public void displayValues(){
try{
t1.setText(String.valueOf(rs.getInt(1)));
t2.setText(rs.getString(2));
t3.setText(rs.getString(3));
t4.setText(String.valueOf(rs.getInt(4)));
} catch(Exception e){System.out.println(e.toString());}
}
}
40
Working with ResultSetMetaData
An object that can be used to get information about the types and properties of the columns
in a ResultSet object.
An example code to show the usage of ResultSetMetaData
import java.sql.*;
public class jdbcinfo
{
Connection conn;Statement stmt;ResultSet rs;ResultSetMetaData rsm;
public jdbcinfo()
{
try{
conn=DriverManager.getConnection("jdbc:odbc:oradsn","scott","tiger");
stmt=conn.createStatement();rs=stmt.executeQuery("select * from emp");
rsm=rs.getMetaData();
int val=rsm.getColumnCount();
for(int i=1;i<=val;i++)
{
System.out.print(rsm.getColumnName(i)+" ");
System.out.print(rsm.getColumnTypeName(i)+" ");
}
conn.close();
}
catch(Exception e){System.out.println(e.toString());}
}
public static void main(String args[]){jdbcinfo ji=new jdbcinfo();}}
41
Working with ResultSetMetaData
Following are the few useful methods to work with ResultSetMetaData:
Method
getColumnCount()
Return Type
Purpose
int
To know the number of columns in this ResultSet object
getColumnName(int col)
String
getColumnType(int col)
int
getColumnTypeName(int col)
String
Get the designated column's name

Retrieves the designated column's SQL type
Retrieves the designated column's database-specific
type name
getPrecision(intcol)
int
Get the designated column's number of decimal digits
getScale(intcol)
int
Gets the designated column's number of digits to

right of the decimal point
getTableName(intcol)
String
Gets the designated column's table name
42
Working With DatabaseMetaData
DatabaseMetaData interface provides methods to get meta data of a database such as

database product name, database product version, driver name, name of total number of
tables, name of total number of views etc.
Commonly used methods of DatabaseMetaData interface :
public String getDriverName()throws SQLException:it returns the name of the JDBC driver.
public String getDriverVersion()throws SQLException:it returns the version number of the JDBC driver.
public String getUserName()throws SQLException:it returns the username of the database.
public String getDatabaseProductName()throws SQLException:it returns the product name of the
database.
public String getDatabaseProductVersion()throws SQLException:it returns the product version of the
database
How to get the object of DatabaseMetaData:
The getMetaData() method of Connection interface returns the object of DatabaseMetaData.
Syntax:
publicDatabaseMetaDatagetMetaData()throwsSQLException
43
Example on DataBaseMetaData
importjava.sql.*;
classDbmd{
publicstaticvoidmain(Stringargs[]){
try{
Connectioncon=DriverManager.getConnection(
"jdbc:oracle:thin:@localhost:1521:xe","system","oracle");
DatabaseMetaDatadbmd=con.getMetaData();
System.out.println("DriverName:"+dbmd.getDriverName());
System.out.println("DriverVersion:"+dbmd.getDriverVersion());
System.out.println("UserName:"+dbmd.getUserName());
System.out.println("DatabaseProductName:"+dbmd.getDatabaseProductName());
System.out.println("DatabaseProductVersion:"+dbmd.getDatabaseProductVersion());
con.close();
}catch(Exceptione){System.out.println(e);}
}
}
44
Scrollable ResultSet
JDBC 2.0 made enhancements to resultsets by introducing scrollability, positioning, and

concurrency capabilities. This sub-section discusses the first two enhancements of
scrollability and positioning. The next sub-section discusses the enhanced feature of
concurrency or updateable resultsets.
Scrollability refers to moving forwards or backwards through rows in a resultset.
Positioning refers to moving the current row position to a different position by jumping to
a specific row. These two features are provided by means of three additional method calls,
one each for createStatement(), prepareStatement(), and prepareCall() methods. These
new methods take two new parameters namely, the resultSetType and
resultSetConcurrency. The definition of these new methods is as follows:
connection.createStatement(int resultSetType, int resultSetConcurrency);
connection.prepareStatement(String sql, int resultSetType, int resultSetConcurrency);
connection.prepareCall(String sql, int resultSetType, int resultSetConcurrency);
45
The parameter resultSetType determines whether a resultset is scrollable or not. It can take
one of the following three values only:
ResultSet.TYPE_FORWARD_ONLY
ResultSet.TYPE_SCROLL_SENSITIVE
specifies that a resultset is not scrollable, that is,

rows within it can be advanced only in the forward
direction.
specifies that a resultset is scrollable in either
direction but is insensitive to changes committed
by other transactions or other statements in the
same transaction.
specifies that a resultset is scrollable in either
direction and is affected by changes committed by
other transactions or statements within the same
transaction.
46
The second parameter resultSetConcurrency determines whether a resultset is
updateable or not and can take one of the two values only:
ResultSet.CONCUR_UPDATEABLE
With these resultset types and two concurrency types, there are six different kinds of
resultsets that can be defined. These are :
Type_Forward_Only/Concur_Read_Only
Type_Forward_only/Concur_Updateable
Type_Scroll_Insensitive/Concur_Read_Only
Type_Scroll_Insensitive/Concur_Updateable
Type_Scroll_Sensitive/Concur_Read_Only
Type_Scroll_Sensitive/Concur_Updateable
47
A scrollable resultset allows for random access to its rows. Random access in turn allows for accessing a
particular row directly without having to advance row by row. This direct positioning of control at a
specific row is termed positioning.
To enable scrollability and positioning, in JDBC 2.0, the ResultSet class provides a set of new methods in
addition to the next() method available in JDBC 1.0. These methods are as follows:
first()
Positions the control at the first row in the resultset and returns true. If there are
no rows in the resultset, it returns false.
last()
Positions the control at the last row in the resultset and returns true. If there are
no rows in the resultset, it returns false.
previous()
Positions the control at the previous row in the resultset relative to the current
row. This returns true if the previous row exists. It returns false, if it causes the
resultset to be positioned before the first row.
absolute(int row)
relative(int offset)
Directly jumps to the row specified by the parameter. This is absolute positioning,
meaning it jumps to the row specified starting from the beginning or end
depending on whether the parameter is positive or negative. This returns true if
the row jumped to is valid. If a zero is passed, it throws an exception. Remember
that absolute(1) is same as first() and absolute(-1) is same as last().
Directly jumps to the row starting from the current row by an offset specified by
the parameter. This is relative positioning meaning, it jumps to the row specified
starting from the current row.
48
Assignment
A Frame based modular JDBC demo application
A Frame based modular JDBC demo application
MainModule
SelectModule
InsertModule
UpdateModule
DeleteModule
49
Updateable ResultSet
Updateable resultsets means the ability to update the contents of specific row(s) in the
resultset and propagating these changes to the underlying database.
This capability is supported in JDBC 2.0 only. Also the operations of INSERT and
DELETE are possible. New rows can be inserted into the underlying table and existing
rows can be deleted from both the resultset as well as the underlying table.
The CLASSPATH has to include classes12.zip for using updateable resultsets.
Java Code
Database
TABLE
INSERT
UPDATE
SQL Query
DELETE
--------- ----------------------- -------------
Selected Row(s)
ResultSet
50
Update Operation through a ResultSet
The following are the steps involved in creating and using an updateable ResultSet:
STEP 1
Create Updateable ResultSet

Create Updateable ResultSet
To create an updateable resultset, the resultSetConcurrency parameter has to be specified

as ResulSet.CONCUR_UPDATEABLE while defining the createStatement(),
preparedStatement() or prepareCall() method on the Connection object.
This is shown below:
Connection conn = null;
Connection conn = null;
//Load and register Oracle driver
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
//Establish a connection
conn = DriverManager.getConnection("jdbc:oracle:thin:@training:1521:9iserver", scott", tiger");
conn = DriverManager.getConnection("jdbc:oracle:thin:@training:1521:9iserver", scott", tiger");
Statement stmt =
Statement stmt =
conn.createStatement(Resultset.TYPE_SCROLL_SENSITIVE,ResultSet.CONCUR_UPDATEABLE);
conn.createStatement(Resultset.TYPE_SCROLL_SENSITIVE,ResultSet.CONCUR_UPDATEABLE);
String sql = ...
String sql = ...
ResultSet rset = stmt.executeQuery(sql);
ResultSet rset = stmt.executeQuery(sql);
51
Update Operation through a ResultSet

STEP 2
Set the values of the ResultSet Clumns

Set the values of the ResultSet Clumns
Use the updateXXX() (for example, updateInt() and updateString()) methods on the
ResultSet object to set the values of the resultset columns. JDBC 2.0 has provided these
methods for each of the Java primitive types as well for some SQL types that correspond
to Java objects.
rset.updateFloat(2, new_val);
The use of this method is as follows:
rset.updateFloat(2, new_val);
Here 2 refers to the

Here 2 refers to the
second column in the
second column in the
resultset.
resultset.
STEP 3
new_val is a variable that holds a new

new_val is a variable that holds a new
value to which this column data is to be
value to which this column data is to be
set to.
set to.
Propagate the changes made to the resultset to the underlying database table
Propagate the changes made to the resultset to the underlying database table
Use the updateRow() method on the ResultSet object to propagate the changes made to
the resultset to the underlying database table and commit them. This has to be done once
for each row in the resultset that is changed.
The use of this method is as follows:
rset.updateRow();
rset.updateRow();
52
Updating through ResultSet by Example
UpdateableResultSetExampl
import java.sql.*;
e.java
public class UpdateableResultSetExample {
public static void main(String[] args) throws SQLException {
int ret_code; Connection conn = null;
try {
String cs="jdbc:oracle:thin:@training:1521:Oracle";
conn = DriverManager.getConnection(cs,scott", "tiger");
int i_deptno = 10;
String sql = "SELECT empno, sal, comm FROM emp_with_type WHERE deptno = ?" ;
PreparedStatement pstmt = conn.prepareStatement(sql, ResultSet.TYPE_SCROLL_SENSITIVE,
ResultSet.CONCUR_UPDATEABLE);
pstmt.setInt(1, i_deptno); ResultSet rset = pstmt.executeQuery();
while (rset.next()) {
float i_sal = rset.getFloat(2);
float i_comm = rset.getFloat(3);
rset.updateFloat(2, (float)(i_sal+(1.25*i_comm)));
rset.updateRow();
} // End of the while loop.
rset.close(); pstmt.close(); pstmt.close(); conn.close();
} // End of the try block.
catch (SQLException e) { ret_code = e.getErrorCode(); System.err.println(ret_code + e.getMessage());
conn.close();}
} // End of the main method.
} // End of the class.
53
Inserting row through ResultSet
A new row can be inserted into the underlying database table through a resultset.
The steps involved are:
STEP 1
Navigate to the insert row. This is done by using the method moveToInsertRow() on the
ResultSet object. The insert row is a special row in the resultset and is different from the
existing rows in the resultset that have been returned by the query. After the insert, the
control can be made to navigate to the current row (i.e., the row before moving to the
new insert row) using the method moveToCurrentRow() on the ResultSet object.
STEP 2
Update the contents of this insert row by using the updateXXX() methods on the
ResultSet object.
STEP 3
Apply the new row to the database by using insertRow() method on the ResultSet
object.
Inserting a new row through a resultset

Inserting a new row through a resultset
only adds the row to the database, and
only adds the row to the database, and
not to the resultset. The new row is visible
not to the resultset. The new row is visible
in the resultset only; it's selected as part
in the resultset only; it's selected as part
of a new query that is executed again.
of a new query that is executed again.
Tips
If auto-commit is enabled, the new row is

If auto-commit is enabled, the new row is
committed immediately by calling
committed immediately by calling
insertRow(). If auto-commit is disabled,
insertRow(). If auto-commit is disabled,
changes can be committed or rolled back.
changes can be committed or rolled back.
Navigating to a different row cancels the
Navigating to a different row cancels the
current changes.
current changes.
54
Deleting row through ResultSet

A row in a resultset can be deleted as follows:
STEP 1
Navigate to the specific row. As you did it previously in case of INSERT.
STEP 2
Delete the row using the deleteRow() method on the ResultSet object.
Tips
Deleting a row from the resultset implicitly deletes the corresponding row
Deleting a row from the resultset implicitly deletes the corresponding row
from the database table. This is unlike updating or inserting rows through a
from the database table. This is unlike updating or inserting rows through a
resultset, when the changes made to the resultset have to be explicitly
resultset, when the changes made to the resultset have to be explicitly
applied to the database using updateRow() or insertRow() methods.
applied to the database using updateRow() or insertRow() methods.
55
Example To Store File In Oracle DB
The setCharacterStream() method of PreparedStatement is used to set character

information into the parameterIndex
CREATETABLE"FILETABLE"
("ID"NUMBER,
"NAME"CLOB
)
/
publicclassStoreFile{
publicstaticvoidmain(String[]args){
try{
Connectioncon=DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe","system","oracle");
PreparedStatementps=con.prepareStatement("insertintofiletablevalues(?,?)");
Filef=newFile("d:\\myfile.txt");
FileReaderfr=newFileReader(f);ps.setInt(1,101);
ps.setCharacterStream(2,fr,(int)f.length()); inti=ps.executeUpdate();
System.out.println(i+"recordsaffected");con.close();
}
catch(Exceptione){e.printStackTrace();}
}
}
56
Example To Retrieve File From Oracle DB
The getClob() method of PreparedStatement is used to get file information from the
database.
Syntax of getClob method
publicClobgetClob(intcolumnIndex){}
CREATETABLE"FILETABLE"
("ID"NUMBER,
"NAME"CLOB
)
/
57
Example To Retrieve File From Oracle DB Cont

publicclassRetrieveFile{
try{
Connectioncon=DriverManager.getConnection(
"jdbc:oracle:thin:@localhost:1521:xe","system","oracle");
PreparedStatementps=con.prepareStatement("select*fromfiletable");
ResultSetrs=ps.executeQuery();
rs.next();//nowon1strow
Clobc=rs.getClob(2);
Readerr=c.getCharacterStream();
FileWriterfw=newFileWriter("d:\\retrivefile.txt");
int i;
while((i=r.read())!=-1)
fw.write((char)i);
fw.close();
con.close();
System.out.println("success");
}catch(Exceptione){e.printStackTrace();}}}
58
Example to Store Image in Oracle DB

You can store images in the database in java by the help ofPreparedStatement
interface.
ThesetBinaryStream()method of PreparedStatement is used to set Binary
information into the parameterIndex.
The syntax of setBinaryStream() method is given below:
1. publicvoidsetBinaryStream(intparamIndex,InputStreamstream)throwsSQLException
2. publicvoidsetBinaryStream(intparamIndex,InputStreamstream,longlength)
throwsSQLException
59
Example To Store Image In Oracle DB

For storing image into the database, BLOB (Binary Large Object) datatype is used
in the table.
CREATETABLE"IMGTABLE"
("NAME"VARCHAR2(4000),
"PHOTO"BLOB
)
Let's write the jdbc code to store the image in the database. Here we are using
d:\\d.jpg for the location of image. You can change it according to the image
location
60
Example To Store Image In Oracle DB

importjava.sql.*;
importjava.io.*;
publicclassInsertImage{
try{
Connectioncon=DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe","system","oracle");
PreparedStatementps=con.prepareStatement("insertintoimgtablevalues(?,?)");
ps.setString(1,rahim");
FileInputStreamfin=newFileInputStream("d:\\g.jpg");
ps.setBinaryStream(2,fin,fin.available());
inti=ps.executeUpdate();
System.out.println(i+"recordsaffected");
con.close();
}
catch(Exceptione){e.printStackTrace();}
}}
61
Example To Retrieve Image From Oracle DB

By the help ofPreparedStatementwe can retrieve and store the image in the
database.
ThegetBlob()method of PreparedStatement is used to get Binary information, it
returns the instance of Blob. After calling thegetBytes()method on the blob
object, we can get the array of binary information that can be written into the
image file.
Signature of getBlob() method of PreparedStatement
publicBlobgetBlob()throwsSQLException
Signature of getBytes() method of Blob interface
publicbyte[]getBytes(longpos,intlength)throwsSQLException
62

We are assuming that image is stored in the imgtable.
CREATETABLE"IMGTABLE"
("NAME"VARCHAR2(4000),
"PHOTO"BLOB
)
Now let's write the code to retrieve the image from the database and write it into
the directory so that it can be displayed.
63

importjava.sql.*;
importjava.io.*;
publicclassRetrieveImage{
try{Class.forName("oracle.jdbc.driver.OracleDriver");
Connectioncon=DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe","system","oracle")
;
PreparedStatementps=con.prepareStatement("select*fromimgtable");
ResultSetrs=ps.executeQuery();
if(rs.next()){//nowon1strow
Blobb=rs.getBlob(2);//2means2ndcolumndata
bytebarr[]=b.getBytes(1,(int)b.length());//1meansfirstimage
FileOutputStreamfout=newFileOutputStream("d:\\rahim.jpg");
fout.write(barr);fout.close();
}//endofif
System.out.println("ok");
con.close();
}catch(Exceptione){e.printStackTrace();}
}
}
64
Calling PL/SQL
65
Calling Stored Procedure
Stored procedures are part and parcel of any database application that enables a lot of
business logic to be stored as application logic in the database in compiled form. This
section highlights the calling of PL/SQL stored procedures.
PL/SQL stored procedures are called from within JDBC programs by means of the
prepareCall() method of the Connection object created above. A call to this method takes
variable bind parameters as input parameters as well as output variables and creates an
object instance of the CallableStatement class.
Calling Stored Procedure

Database
Java Application
Call to procedure
procedure
table
Return value
through its
OUT parameter
66
Calling Stored Procedure by Example

create or replace procedure calcGross(eno in number, gross out number)
Is
Begin
Select sal+nvl(comm,0) Into gross
From emp Where empno = eno;
End;
Create the procedure

The JDBC Code
import java.sql.*;
public class CallProcedure{
public static void main(String args[]) throws Exception{
String cs = "jdbc:oracle:thin:@oracle9iserver:1521:orcl"; String driver =
"oracle.jdbc.driver.OracleDriver";
String uname = "scott"; String pword = "tiger";
Class.forName(driver); Connection conn = DriverManager.getConnection(cs, uname, pword);
CallableStatement s =conn.prepareCall("{call calcGross(?,?)}");
int no;
for(int i=0; i < args.length;i++){
no = Integer.parseInt(args[i]);
s.setInt (1, no);
s.registerOutParameter (2, Types.INTEGER);
s.executeUpdate();
int totsal = s.getInt(2);
System.out.println(totsal);}}}
67
Lets test the code

dos_prompt>javac CallProcedure.java
Compile the code

Execute the code
dos_prompt>java CallProcedure 7369 7844
This will display the sal+nvl(comm,0) for empno 7369 and 7844. You can provide n
numbers of empno to display the value of their sal+nvl(comm,0).
Output
68
Calling Stored Function returning a Ref-Cursor

What is an Oracle REF CURSOR?
Calling a function that returns a ref-cursor
A REF CURSOR is a weakly typed cursor type that identifies a cursor variable. A variable
A REF CURSOR is a weakly typed cursor type that identifies a cursor variable. A variable
can defined of the REF CURSOR type and then a query can be opened for it. The cursor
can defined of the REF CURSOR type and then a query can be opened for it. The cursor
variable then acts as a pointer to the query or SELECT thus opened. Stored procedures
variable then acts as a pointer to the query or SELECT thus opened. Stored procedures
or functions as well as packaged procedures or functions can return cursor variables of
or functions as well as packaged procedures or functions can return cursor variables of
type REF CURSOR. The output consists of a ResultSet that holds the rows returned by
type REF CURSOR. The output consists of a ResultSet that holds the rows returned by
the REF CURSOR. This output can be captured in a JDBC ResultSet object.
the REF CURSOR. This output can be captured in a JDBC ResultSet object.
Database
Java Application
Call to function
function
Return ref-cursor
table
69
Calling Stored Function by Example

CREATE OR REPLACE PACKAGE pkg
AS
TYPE ref_cursor IS REF CURSOR;
END;
Create an Oracle type of REF CURSOR type

Create a function with return type REF CURSOR
CREATE OR REPLACE FUNCTION get_emp(dno IN NUMBER) RETURN pkg.ref_cursor

AS
emp_cursor pkg.ref_cursor;
BEGIN
OPEN emp_cursor FOR SELECT empno,ename,job FROM emp WHERE deptno = dno;
RETURN emp_cursor;
END;
Do the following from SQL prompt for testing
var results refcursor
Declares a variable
Declares a variable
exec :results := get_emp(20)
executes the function and keeps the

executes the function and keeps the
returned value in it
returned value in it
print results
displays the output

displays the output
70
Call the function from a Java Code
import java.sql.*;
public class RefCursorExample{
public static void main(String[] args) throws Exception{
try{
conn = DriverManager.getConnection("jdbc:oracle:thin:@sedev1:1521:orcl9","scott","tiger");
int xdeptno = Integer.parseInt(args[0]);CallableStatement cstmt = conn.prepareCall("{? = call get_emp(?)}");
cstmt.registerOutParameter(1, OracleTypes.CURSOR);
cstmt.setInt(2, xdeptno);
cstmt.executeUpdate(); ResultSet rset;
rset = (ResultSet) cstmt.getObject(1); ResultSetMetaData rsmd = rset.getMetaData();
int colcount = rsmd.getColumnCount();
while (rset.next()){
String str = "";
for(int i=1;i<=colcount;i++){
if(i!=colcount)
str=str+rset.getString(i)+" | ";
else
str=str+rset.getString(i);
}
System.out.println(str);
}
rset.close(); cstmt.close(); conn.close();
}
catch (Exception e) {System.out.println(e.toString()); conn.close();}
}
}
71
Batch Update & Transaction
72
Performing Batch Updates
One of the more advanced features of JDBC 2.0 is the ability to submit multiple update
statements to the database for processing as a single unit. This batch updating can be
significantly more efficient compared to JDBC 1.0, where each update statement has to be
executed separately.
Connection Channel
Insert Into emp(empno,ename) Values(1111,Amit)

Insert Into emp(empno,ename) Values(1111,Amit)
Insert Into emp(empno,ename) Values(1112,Binay)
Insert Into emp(empno,ename) Values(1112,Binay)
Insert Into emp(empno,ename) Values(1113,Chiranjeeb)
Insert Into emp(empno,ename) Values(1113,Chiranjeeb)
Insert Into emp(empno,ename) Values(1114,Dinesh)
Insert Into emp(empno,ename) Values(1114,Dinesh)
Database
Batch of statements
Batch of statements
All the four rows are going
to be inserted with the
invocation of a single
executeBatch() method
table
73
Batch Update by Example
TestBatchUpdate.java
import java.sql.*;
public class TestBatchUpdate
{
public static void main(String args[]) throws SQLException
{
Connection conn=null;
Statement stmt;
try
{
conn=DriverManager.getConnection("jdbc:odbc:empdsn","","");
conn.setAutoCommit(false);
stmt = conn.createStatement();
stmt.addBatch("Insert Into emp(empno,ename) Values(1111,Amit)");
stmt.addBatch("Insert Into emp(empno,ename) Values(1112,Binay)");
int result[]=stmt.executeBatch();
conn.commit();
stmt.close();
conn.close();
}
catch(BatchUpdateException e){System.out.println("Exception 1: " + e.toString()); conn.rollback();}
catch(SQLException e){System.out.println("Exception 2: " + e.toString());conn.rollback();}
catch(ClassNotFoundException e){System.out.println("Exception 3: " + e.toString());conn.rollback();}}
74
Jdbc
RowSet
The instance ofRowSetis the java bean component because it has properties and
java bean notification mechanism
It is introduced in JDBC 3.0

It is the wrapper of ResultSet. It holds tabular data like ResultSet but it is easy and
flexible to use
The advantages of using RowSet
It is easy and flexible to use
It is Scrollable and Updatable bydefault
75
RowSet by Example
import javax.sql.rowset.JdbcRowSet;
import javax.sql.rowset.RowSetProvider;
public class JdbcRowSetEx {
public static void main(String[] args) throws Exception {
JdbcRowSet rowSet = RowSetProvider.newFactory().createJdbcRowSet();
rowSet.setUrl("jdbc:oracle:thin:@rbmtrain:1521:trng1");
rowSet.setUsername("oracle2");
rowSet.setPassword("ora123");
rowSet.setCommand("select * from emp");
rowSet.execute();
while (rowSet.next()) {
System.out.println(rowSet.getInt(1) + "...." + rowSet.getString(2));
}
}
}
76
Using
Transactions
A transaction is a collection of DML statements that are executed as if they are a single
operation.
A JDBC application that needs to execute multiple SQL statements targeted towards a
specific function, can make use of JDBC's transaction services.
Transactions might need to be grouped in situations where multiple updates are needed
and the entire set of transactions is to be committed or the entire set undone in case of a
single failure.
Transaction services basically include beginning the transaction, executing the SQL
statements that make up the transaction, and either perform a commit on overall success
of each SQL statement or rollback the transaction as a whole if one of the SQL statements
fails.
Transaction management in JDBC is handled to some extent by the Connection object.
Whenever a new Connection is opened, the transaction auto-commit mode is turned on.
In auto-commit mode, every SQL statement is executed as a single transaction that is
immediately committed to the database.
To execute multiple SQL statements as part of a single transaction, the auto-commit is to
be disabled.
77
Using Transactions
Committing
Committing of DML INSERT, UPDATE, or DELETE statements in JDBC

programs is done automatically. The auto-commit is set to ON by default
in JDBC and a COMMIT is issued after every SQL operation. However, if
you choose to set the auto-commit mode off, you can do so by calling
the setAutoCommit() of the Connection object as follows:
The above line of code should appear immediately after the connection has been
established. This is shown below :
conn = DriverManager.getConnection("jdbc:oracle:thin:@training:1521:Oracle","scott","tiger");
//Disable auto-commit mode
Once the auto-commit mode is turned off, an explicit COMMIT or ROLLBACK should be
done to commit any unsaved database changes. COMMIT or ROLLBACK can be done by
calling the commit() or rollback() methods of the Connection object.
78
Transaction
Management
by
Example
import java.sql.*;
import java.sql.*;
public class TransactionExample {
public class TransactionExample {
try{ DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
try{ DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
conn = DriverManager.getConnection("jdbc:oracle:thin:@training:1521:Oracle", "scott", "tiger");
conn = DriverManager.getConnection("jdbc:oracle:thin:@training:1521:Oracle", "scott", "tiger");
conn.setAutoCommit(false); // Disable auto-commit mode
conn.setAutoCommit(false); // Disable auto-commit mode
String sql1 = "SELECT empno FROM emp WHERE empno = ?" ;
String sql1 = "SELECT empno FROM emp WHERE empno = ?" ;
String sql2 = "INSERT INTO emp VALUES (?,?,?,?,?,?,?,?)";
String sql2 = "INSERT INTO emp VALUES (?,?,?,?,?,?,?,?)";
String sql3 = "UPDATE dept_audit SET cnt_emp = nvl(cnt_emp,0) + 1 WHERE deptno = 10";
String sql3 = "UPDATE dept_audit SET cnt_emp = nvl(cnt_emp,0) + 1 WHERE deptno = 10";
PreparedStatement pstmt1 = conn.prepareStatement(sql1);
pstmt1.setInt(1, 9999); ResultSet rset = pstmt1.executeQuery();
pstmt1.setInt(1, 9999); ResultSet rset = pstmt1.executeQuery();
if(rset.next()){
if(rset.next()){
System.out.println("The employee with empno 9999 already exists."); rset.close();
System.out.println("The employee with empno 9999 already exists."); rset.close();
}
}
else{
pstmt2.setInt(1, 9999);
pstmt2.setString(2, "CHARLIE");
else{
pstmt2.setString(2, "CHARLIE");
pstmt2.setString(3, "ANALYST");
pstmt2.setString(3, "ANALYST");
pstmt2.setString(5, "01-JAN-01");
pstmt2.setFloat(6, 12000);
pstmt2.setString(5, "01-JAN-01");
pstmt2.setFloat(6, 12000);
pstmt2.setFloat(7, (float)10.5);
pstmt2.setFloat(7, (float)10.5);
pstmt2.executeUpdate();
}
}
pstmt1.close();
pstmt2.close();
pstmt3.close();
pstmt1.close();
pstmt2.close();
pstmt3.close();
>>
79
Transaction Management by Example

Remaining part of the code
// Commit the effect of all both the INSERT and UPDATE statements together
// Commit the effect of all both the INSERT and UPDATE statements together
conn.commit();
conn.commit();
conn.close();
conn.close();
}
}
}
}
catch (SQLException e)
catch (SQLException e)
{
{
// Rollback all the changes so as to undo the effect of both INSERT and UPDATE
// Rollback all the changes so as to undo the effect of both INSERT and UPDATE
conn.rollback();
conn.rollback();
ret_code = e.getErrorCode();
ret_code = e.getErrorCode();
System.out.println(ret_code + e.getMessage()); conn.close();
System.out.println(ret_code + e.getMessage()); conn.close();
}
}
80
Using Savepoints
The new JDBC 3.0 Savepoint interface gives you additional transactional
control.DBMS support savepoints within their environments such as Oracle's
PL/SQL.
Traditionally, database transactions have been "all or nothing" types of events.
An application would start a transaction, it might insert some rows, do some
updates, and then either make the changes permanent or discard all of the
changes.
Either all of the changes would be made permanent or none of the changes
would be permanent.
With JDBC 3.0, the transactional model is now more flexible. An application
might start a transaction, insert several rows and then create a savepoint.
81
Using Savepoints contd..
This savepoint serves as a bookmark. With JDBC 2.0, the application would now
have to either commit all the changes or rollback all the changes. With JDBC 3.0,
the application might conclude that the updates made were a bad idea but the
initial inserts were okay.
The application can rollback to the savepoint and, then, commit the group of
inserts as if the updates have never been attempted.
The Connection object has new methods
setSavepoint(String savepointName)
releaseSavepoint(Savepoint savepointName)
rollback (String savepointName)
82
SavePoints by Example
try{
try{
//Assume a valid connection object conn
//Assume a valid connection object conn
Statement stmt = conn.createStatement();
Statement stmt = conn.createStatement();
//set a Savepoint
//set a Savepoint
Savepoint savepoint1 = conn.setSavepoint("Savepoint1");
Savepoint savepoint1 = conn.setSavepoint("Savepoint1");
String SQL = "INSERT INTO Emp " + "VALUES (7654, Rahim, Syed)";
String SQL = "INSERT INTO Emp " + "VALUES (7654, Rahim, Syed)";
stmt.executeUpdate(SQL);
//Submit a malformed SQL statement that breaks
//Submit a malformed SQL statement that breaks
String SQL = "INSERTED IN Emp " + "VALUES (8765,Karim, Syed)";
String SQL = "INSERTED IN Emp " + "VALUES (8765,Karim, Syed)";
// If there is no error, commit the changes.
// If there is no error, commit the changes.
conn.commit();
conn.commit();
}
}
catch(SQLException se){
catch(SQLException se){
// If there is any error.
// If there is any error.
conn.rollback(savepoint1);
conn.rollback(savepoint1);
}
}
83
Connection Pooling
Opening a connection to a database is a time-consuming process. For short queries, it can take
Opening a connection to a database is a time-consuming process. For short queries, it can take
much longer to open the connection than to perform the actual database retrieval. Consequently,
much longer to open the connection than to perform the actual database retrieval. Consequently,
it makes sense to reuse Connection objects in applications that connect repeatedly to the same
it makes sense to reuse Connection objects in applications that connect repeatedly to the same
database.
database.
If a connection is required and an idle connection is available, put it in the list of busy connections
If a connection is required and an idle connection is available, put it in the list of busy connections
and then return it. The busy list is used to check limits on the total number of connections as well
and then return it. The busy list is used to check limits on the total number of connections as well
as when the pool is instructed to explicitly close all connections.
as when the pool is instructed to explicitly close all connections.
One caveat: connections can time out, so before returning the connection, confirm that it is still
One caveat: connections can time out, so before returning the connection, confirm that it is still
open. If not, discard the connection and repeat the process. Discarding a connection opens up a
open. If not, discard the connection and repeat the process. Discarding a connection opens up a
slot that can be used by processes that needed a connection
slot that can be used by processes that needed a connection
when the connection limit had been reached, so use notifyAll to tell all waiting threads to wake up
when the connection limit had been reached, so use notifyAll to tell all waiting threads to wake up
and see if they can proceed.
and see if they can proceed.
If a connection is required, there is no idle connection available, and the connection limit has not
If a connection is required, there is no idle connection available, and the connection limit has not
been reached, then start a background thread to allocate a new connection. Then, wait for the
been reached, then start a background thread to allocate a new connection. Then, wait for the
first available connection, whether or not it is the newly allocated one.
first available connection, whether or not it is the newly allocated one.
This situation occurs when there is no idle connection and youve reached the limit on the number
This situation occurs when there is no idle connection and youve reached the limit on the number
of connections. The natural approach is to use the wait method, which gives up the thread
of connections. The natural approach is to use the wait method, which gives up the thread
synchronization lock and suspends the thread until notifyAll is called.
synchronization lock and suspends the thread until notifyAll is called.
84
The Connection Pool Class Definition
import java.sql.*;
import java.sql.*;
import java.util.*;
import java.util.*;
public class ConnectionPool
public class ConnectionPool
{
Vector freeconnection; Vector busyconnection; String driver, url, user, password;
{
Vector freeconnection; Vector busyconnection; String driver, url, user, password;
ConnectionPool(String driver, String url, String user, String password)
ConnectionPool(String driver, String url, String user, String password)
{
this.driver=driver; this.url=url;
{
this.driver=driver; this.url=url;
this.user=user;
this.password=password;
this.user=user;
this.password=password;
freeconnection = new Vector(5);
busyconnection = new Vector();
freeconnection = new Vector(5);
busyconnection = new Vector();
for(int i=0; i<5; i++)
for(int i=0; i<5; i++)
{
freeconnection.addElement(createConnection());
{
}
}
}
}
private Connection getConnection()
private Connection getConnection()
{
try{
Class.forName(driver);
{
try{
Class.forName(driver);
return DriverManager.getConnection(url,user,password);
return DriverManager.getConnection(url,user,password);
}
}
catch(Exception ex){
catch(Exception ex){
System.out.println("1 : "+ex.toString());
System.out.println("1 : "+ex.toString());
return null;
return null;
}
}
}
}
85
public synchronized Connection getConnection() throws Exception{

public synchronized Connection getConnection() throws Exception{
int flag = 0; Connection conn=null;
int flag = 0; Connection conn=null;
while(flg==0){
while(flg==0){
if(freeconnection.size()==0)
if(freeconnection.size()==0)
{
try{wait();}catch(Exception ex){System.out.println("2 : ex.toString());}
{
try{wait();}catch(Exception ex){System.out.println("2 : ex.toString());}
}
}
else
else
{
conn=(Connection)freeconnection.elementAt(0);
{
conn=(Connection)freeconnection.elementAt(0);
if(conn.isClosed())
if(conn.isClosed())
{
freeconnection.remove(0);
{
freeconnection.remove(0);
}
}
else
else
{
busyconnection.addElement(conn);freeconnection.remove(0);
{
busyconnection.addElement(conn);freeconnection.remove(0);
flag=1;
flag=1;
}
}
}
}
}
}
return conn;
return conn;
}
}
86
public synchronized void releaseConnection(Connection c)

public synchronized void releaseConnection(Connection c)
{
if(busyconnection.contains(c))
{
if(busyconnection.contains(c))
{
int index = busyconnection.indexOf(c);
{
int index = busyconnection.indexOf(c);
freeconnection.addElement(c);
freeconnection.addElement(c);
busyconnection.remove(index);
busyconnection.remove(index);
notifyAll();
notifyAll();
System.out.println("Connection Released!!!");
System.out.println("Connection Released!!!");
}
}
else
else
{
System.out.println("Invalid Connection !!!!!");
{
System.out.println("Invalid Connection !!!!!");
}
}
}
}
}
End of the connection pool
87
Using Connection Pool Class
import java.sql.*;
import java.sql.*;
public class TestConnectionPool{
public class TestConnectionPool{
String driver = "oracle.jdbc.driver.OracleDriver";
String driver = "oracle.jdbc.driver.OracleDriver";
String url ="jdbc:oracle:thin:@10.131.211.116:1521:oracle";
String url ="jdbc:oracle:thin:@10.131.211.116:1521:oracle";
String user="scott"; String password="tiger";
String user="scott"; String password="tiger";
ConnectionPool cp = new ConnectionPool(driver,url,user,password);
ConnectionPool cp = new ConnectionPool(driver,url,user,password);
String s1="Select empno, ename from emp;
String s1="Select empno, ename from emp;
String s2=" Select empno, job from emp where deptno=30;
String s2=" Select empno, job from emp where deptno=30;
String s3=" Select empno, hiredate from emp where deptno=10;
String s3=" Select empno, hiredate from emp where deptno=10;
String s4=" Select empno, sal from emp where deptno=20;
String s4=" Select empno, sal from emp where deptno=20;
String s5=" Select empno, deptno from emp;
String s5=" Select empno, deptno from emp;
String s6=" Select empno, mgr from emp;
String s6=" Select empno, mgr from emp;
new TestConnectionPoolThread(s1,"1st",cp);
new TestConnectionPoolThread(s1,"1st",cp);
new TestConnectionPoolThread(s2,"\t2nd",cp);
new TestConnectionPoolThread(s2,"\t2nd",cp);
new TestConnectionPoolThread(s3,"\t\t3rd",cp);
new TestConnectionPoolThread(s3,"\t\t3rd",cp);
new TestConnectionPoolThread(s4,"\t\t\t4th",cp);
new TestConnectionPoolThread(s4,"\t\t\t4th",cp);
new TestConnectionPoolThread(s5,"\t\t\t\t5th",cp);
new TestConnectionPoolThread(s5,"\t\t\t\t5th",cp);
new TestConnectionPoolThread(s6,"\t\t\t\t\t6th",cp);
new TestConnectionPoolThread(s6,"\t\t\t\t\t6th",cp);
}
}
}
}
88
Using Connection Pool Class
class TestConnectionPoolThread extends Thread{

class TestConnectionPoolThread extends Thread{
ConnectionPool cp; String sql; String msg;
ConnectionPool cp; String sql; String msg;
TestConnectionPoolThread(String sql,String msg,ConnectionPool cp){
TestConnectionPoolThread(String sql,String msg,ConnectionPool cp){
this.cp=cp; this.sql=sql; this.msg=msg;
this.cp=cp; this.sql=sql; this.msg=msg;
start();
start();
}
}
public void run(){
public void run(){
try
try
{ Connection con= cp.retriveConnection();
{ Connection con= cp.retriveConnection();
Statement stmt=con.createStatement();
Statement stmt=con.createStatement();
ResultSet rs= stmt.executeQuery(sql);
ResultSet rs= stmt.executeQuery(sql);
while(rs.next())
while(rs.next())
{
System.out.println(msg+"--"+rs.getInt(1)+"--"+rs.getString(2));
{
System.out.println(msg+"--"+rs.getInt(1)+"--"+rs.getString(2));
sleep(1000);
sleep(1000);
}
}
con.close();
con.close();
cp.releaseConnection(con);
cp.releaseConnection(con);
}
}
catch(Exception e){System.out.println("Error -- "+e );}
catch(Exception e){System.out.println("Error -- "+e );}
}
}
}
}
End of the class definition
89
Course Summary
With this course completed, you should be able to:
Understand the database connectivity from a Java Program
Understand to execute different types of SQL and PL/SQL
query from Java
90
Thank You!
91

JDBC Programming

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

JDBC Programming

Загружено:

Авторское право:

Доступные форматы

JDBC

2015 NetCracker Technology Corporation Confidential

2015 NetCracker Technology Corporation Confidential

Building Connection and Execute Query

2015 NetCracker Technology Corporation Confidential

2015 NetCracker Technology Corporation Confidential

2015 NetCracker Technology Corporation Confidential

2015 NetCracker Technology Corporation Confidential

send SQL code

2015 NetCracker Technology Corporation Confidential

Why Do We Need JDBC?

2015 NetCracker Technology Corporation Confidential

JDBC is Sun's attempt to create a platform-neutral interface between databases

2015 NetCracker Technology Corporation Confidential

2015 NetCracker Technology Corporation Confidential

Install a driver on your machine

Install your DBMS if needed

2015 NetCracker Technology Corporation Confidential

2015 NetCracker Technology Corporation Confidential

2015 NetCracker Technology Corporation Confidential

This is not the

2015 NetCracker Technology Corporation Confidential

2015 NetCracker Technology Corporation Confidential

When a connection is opened, this represents a single instance of a particular

This interface can be used to retrieve information regarding the table

By using Connection a commit is automatic after the execution of a successful

2015 NetCracker Technology Corporation Confidential

SQL statement as string

2015 NetCracker Technology Corporation Confidential

Insert Into emp(empno,ename,job,deptno) Values(?,?,?,?)

2015 NetCracker Technology Corporation Confidential

2015 NetCracker Technology Corporation Confidential

Row for the column heading

2015 NetCracker Technology Corporation Confidential

Initially the pointer will

2015 NetCracker Technology Corporation Confidential

2015 NetCracker Technology Corporation Confidential

JDBC Driver, Making Connection & Execute Query

2015 NetCracker Technology Corporation Confidential

JDBC Driver Type 1

Type 1 : JDBC-ODBC bridge drivers

* The JDBC-ODBC Bridge allows access to almost any

2015 NetCracker Technology Corporation Confidential

JDBC Driver Type 2

Type 2 : Native-API partly Java drivers

* Type 2 drivers typically offer better performance than

2015 NetCracker Technology Corporation Confidential

JDBC Driver Type 3

Type 3 : Net-protocol All-Java drivers

2015 NetCracker Technology Corporation Confidential

JDBC Driver Type 4

Type 4 : Native-protocol All-Java drivers

* Type 4 drivers are completely written in Java to achieve

* Number of translation layers is very less i.e. type 4 JDBC

JDBC Drivers At a glance

JDBC-ODBC bridge drivers

This driver type is the JDBC-ODBC bridge

Native-API partly Java drivers

Native Database library driver

2015 NetCracker Technology Corporation Confidential

JDBC Drivers At a glance

Net-protocol All-Java drivers

100% Java Driver, NO native methods

Native-protocol All-Java drivers