What Is JDBC
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:
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:
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:
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:
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.
The java.sql and javax.sql are the primary packages for JDBC 4.0. This is the latest JDBC version at the time of
writing this tutorial. It offers the main classes for interacting with your data sources.
The new features in these packages include changes in the following areas:
JDBC-SQL Syntex
Structured Query Language (SQL) is a standardized language that allows you to perform operations on a
database, such as creating entries, reading content, updating content, and deleting entries.
SQL is supported by all most any database you will likely use, and it allows you to write database code
independently of the underlying database.
This tutorial gives an overview of SQL, which is a pre-requisite to understand JDBC concepts. This tutorial
gives you enough SQL to be able to Create, Read, Update, and Delete (often referred to as CRUD
operations) data from a database.
For a detailed understanding on SQL, you can read our MySQL Tutorial.
Create Database:
The CREATE DATABASE statement is used for creating a new database. The syntax is:
Example:
Drop Database:
The DROP DATABASE statement is used for deleting an existing database. The syntax is:
Note: To create or drop a database you should have administrator privilege on your database server. Be
careful, deleting a database would loss all the data stored in database.
Create Table:
The CREATE TABLE statement is used for creating a new table. The syntax is:
Example:
The following SQL statement creates a table named Employees with four columns:
SQL> CREATE TABLE Employees
(
id INT NOT NULL,
age INT NOT NULL,
first VARCHAR(255),
last VARCHAR(255),
PRIMARY KEY ( id )
);
Drop Table:
The DROP TABLE statement is used for deleting an existing table. The syntax is:
Example:
INSERT Data:
The syntax for INSERT looks similar to the following, where column1, column2, and so on represent the new
data to appear in the respective columns:
Example:
The following SQL INSERT statement inserts a new row in the Employees database created earlier:
SELECT Data:
The SELECT statement is used to retrieve data from a database. The syntax for SELECT is:
The WHERE clause can use the comparison operators such as =, !=, <, >, <=,and >=, as well as the
BETWEEN and LIKE operators.
Example:
The following SQL statement selects the age, first and last columns from the Employees table where id
column is 100:
The following SQL statement selects the age, first and last columns from the Employees table where first
column contains Zara:
UPDATE Data:
The UPDATE statement is used to update data. The syntax for UPDATE is:
The WHERE clause can use the comparison operators such as =, !=, <, >, <=,and >=, as well as the
BETWEEN and LIKE operators.
Example:
The following SQL UPDATE statement changes the age column of the employee whose id is 100:
DELETE Data:
The DELETE statement is used to delete data from tables. The syntax for DELETE is:
The WHERE clause can use the comparison operators such as =, !=, <, >, <=,and >=, as well as the
BETWEEN and LIKE operators.
Example:
The following SQL DELETE statement delete the record of the employee whose id is 100:
To start developing with JDBC setup your JDBC environment by following the steps shown below. We
assume that you are working on a Windows platform.
Install Java:
Install J2SE Development Kit 5.0 (JDK 5.0) from Java Official Site.
JAVA_HOME: This environment variable should point to the directory where you installed the JDK,
e.g. C:\Program Files\Java\jdk1.5.0
CLASSPATH: This environment variable should has appropriate paths set, e.g. C:\Program
Files\Java\jdk1.5.0_20\jre\lib
PATH: This environment variable should point to appropriate JRE bin, e.g. C:\Program
Files\Java\jre1.5.0_20\bin.
It is possible you have these variable set already, but just to make sure here's how to check.
Go to the control panel and double-click on System. If you are a Windows XP user it's possible you
have to open Performance and Maintenance before you will see the System icon.
Now check all the above mentioned variables are set properly.
You automatically get both JDBC packages java.sql and javax.sql when you install J2SE Development Kit
5.0 (JDK 5.0)
Install Database:
The most important thing you will need, of course is an actual running database with a table that you can
query and modify.
Install a database that is most suitable for you. You can have plenty of choices and most common are:
1. MySQL DB: MySQL is an open source database. You can download it from MySQL Official Site. We
recommend downloading the full Windows installation.
In addition, download and install MySQL Administrator as well as MySQL Query Browser. These are
GUI based tools that will make your development much easier.
Finally, download and unzip MySQL Connector/J (the MySQL JDBC driver) in a convenient directory.
For the purpose of this tutorial we will assume that you have installed the driver at C:\Program
Files\MySQL\mysql-connector-java-5.1.8.
Accordingly set CLASSPATH variable to C:\Program Files\MySQL\mysql-connector-java-5.1.8\mysql-
connector-java-5.1.8-bin.jar. Your driver version may vary based on your installation.
2. PostgreSQL DB: PostgreSQL is an open source database. You can download it from PostgreSQL
Official Site.
The Postgres installation contains a GUI based administrative tool called pgAdmin III. JDBC drivers
are also included as part of the installation.
3. Oracle DB: Oracle DB is an commercial database sold by Oracle . We assume that you have the
necessary distribution media to install it.
Oracle installation includes a GUI based administrative tool called Enterprise Manager. JDBC drivers
are also included as part of the installation.
Now a days most of the Database vendors are supplying appropriate JDBC drivers along with Database
installation. So you should not worry about this part.
Using root ID and password you can either create another users ID and password or you can use root ID
and password for your JDBC application.
There are various database operations like database creation and deletion, which would need administrator
ID and password.
For rest of the JDBC tutorial we would use MySQL Database with username as ID and password as
password.
If you do not have sufficient privilege to create new users then you can ask your Database Administrator
(DBA) to create a user ID and password for you.
Create Database:
To create the EMP database, use the following steps:
Step 1:
C:\>
C:\>cd Program Files\MySQL\bin
C:\Program Files\MySQL\bin>
Note: The path to mysqld.exe may vary depending on the install location of MySQL on your system. You
can also check documentation on how to start and stop your database server.
Step 2:
Start the database server by executing the following command, if it is already not running.
C:\Program Files\MySQL\bin>mysqld
C:\Program Files\MySQL\bin>
Step 3:
Create Table
To create the Employees table in EMP database, use the following steps:
Step 1:
C:\>
C:\>cd Program Files\MySQL\bin
C:\Program Files\MySQL\bin>
Step 2:
Step 3:
mysql>
Now you are ready to start experimenting with JDBC. Next tutorial would give your a sample example on
JDBC Programming.
This tutorial provides an example of how to create a simple JDBC application. This will show you how to
open a database connection, execute a SQL query, and display the results.
All the steps mentioned in this template example, would be explained in subsequent chapters of this tutorial.
1. Import the packages . Requires that you include the packages containing the JDBC classes
needed for database programming. Most often, using import java.sql.* will suffice.
2. Register the JDBC driver . Requires that you initialize a driver so you can open a communications
channel with the database.
3. Open a connection . Requires using the DriverManager.getConnection() method to create a
Connection object, which represents a physical connection with the database.
4. Execute a query . Requires using an object of type Statement for building and submitting an SQL
statement to the database.
5. Extract data from result set . Requires that you use the appropriate ResultSet.getXXX() method
to retrieve the data from the result set.
6. Clean up the environment . Requires explicitly closing all database resources versus relying on
the JVM's garbage collection.
Sample Code:
This sample example can serve as a template when you need to create your own JDBC application in the
future.
This sample code has been written based on the environment and database setup done in previous chapter.
Copy and past following example in FirstExample.java, compile and run as follows:
// Database credentials
static final String USER = "username";
static final String PASS = "password";
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
}
//STEP 6: Clean-up environment
rs.close();
stmt.close();
conn.close();
}catch(SQLException se){
//Handle errors for JDBC
se.printStackTrace();
}catch(Exception e){
//Handle errors for Class.forName
e.printStackTrace();
}finally{
//finally block used to close resources
try{
if(stmt!=null)
stmt.close();
}catch(SQLException se2){
}// nothing we can do
try{
if(conn!=null)
conn.close();
}catch(SQLException se){
se.printStackTrace();
}//end finally try
}//end try
System.out.println("Goodbye!");
}//end main
}//end FirstExample
C:\>javac FirstExample.java
C:\>
C:\>java FirstExample
Connecting to database...
Creating statement...
ID: 100, Age: 18, First: Zara, Last: Ali
ID: 101, Age: 25, First: Mahnaz, Last: Fatma
ID: 102, Age: 30, First: Zaid, Last: Khan
ID: 103, Age: 28, First: Sumit, Last: Mittal
C:\>
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.
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.
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.
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.
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.
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.
After you've installed the appropriate driver, it's time to establish a database connection using JDBC.
The programming involved to establish a JDBC connection is fairly simple. Here are these simple four steps:
1. Import JDBC Packages: Add import statements to your Java program to import required classes
in your Java code.
2. Register JDBC Driver: This step causes the JVM to load the desired driver implementation into
memory so it can fulfill your JDBC requests.
3. Database URL Formulation: This is to create a properly formatted address that points to the
database to which you wish to connect.
4. Create Connection Object: Finally, code a call to the DriverManager object's getConnection( )
method to establish actual database connection.
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:
You need to do this registration only once in your program. You can register a driver in one of two ways.
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.
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);
}
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.
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);
}
1. getConnection(String url)
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
All the highlighted part in URL format is static and you need to change only remaining part as per your
database setup.
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:
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
A third form of the DriverManager.getConnection( ) method requires a database URL and a Properties
object:
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.*;
Relying on garbage collection, especially in database programming, is very poor programming practice. You
should make a habit of always closing the connection with the close() method associated with connection
object.
To ensure that a connection is closed, you could provide a finally block in your code. A finally block always
executes, regardless if an exception occurs or not.
To close above opened connection you should call close() method as follows:
conn.close();
Explicitly closing a connection conserves DBMS resources, which will make your database administrator
happy.
For a better understanding, I would suggest to study our JDBC - Sample Code.
JDBC-Statements
Once a connection is obtained we can interact with the database. The JDBC Statement, CallableStatement,
and PreparedStatement interfaces define the methods and properties that enable you to send SQL or PL/SQL
commands and receive data from your database.
They also define methods that help bridge data type differences between Java and SQL data types used in a
database.
Following table provides a summary of each interface's purpose to understand how do you decide which
interface to use?
Statement Use for general-purpose access to your database. Useful when you are using
static SQL statements at runtime. The Statement interface cannot accept
parameters.
PreparedStatement Use when you plan to use the SQL statements many times. The
PreparedStatement interface accepts input parameters at runtime.
CallableStatement Use when you want to access database stored procedures. The
CallableStatement interface can also accept runtime input parameters.
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:
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.
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.
Following is the example which makes use of following three queries along with opening and closing
statment:
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.
This sample code has been written based on the environment and database setup done in previous chapters.
Copy and past following example in JDBCExample.java, compile and run as follows:
// Database credentials
static final String USER = "username";
static final String PASS = "password";
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
}
//STEP 6: Clean-up environment
rs.close();
stmt.close();
conn.close();
}catch(SQLException se){
//Handle errors for JDBC
se.printStackTrace();
}catch(Exception e){
//Handle errors for Class.forName
e.printStackTrace();
}finally{
//finally block used to close resources
try{
if(stmt!=null)
stmt.close();
}catch(SQLException se2){
}// nothing we can do
try{
if(conn!=null)
conn.close();
}catch(SQLException se){
se.printStackTrace();
}//end finally try
}//end try
System.out.println("Goodbye!");
}//end main
}//end JDBCExample
C:\>javac JDBCExample.java
C:\>
C:\>java JDBCExample
Connecting to database...
Creating statement...
Return value is : false
Rows impacted : 1
ID: 100, Age: 18, First: Zara, Last: Ali
ID: 101, Age: 25, First: Mahnaz, Last: Fatma
ID: 102, Age: 30, First: Zaid, Last: Khan
ID: 103, Age: 30, First: Sumit, Last: Mittal
Goodbye!
C:\>
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.
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.
Following is the example which makes use of PreparedStatement along with opening and closing statments:
This sample code has been written based on the environment and database setup done in previous chapters.
Copy and past following example in JDBCExample.java, compile and run as follows:
// Database credentials
static final String USER = "username";
static final String PASS = "password";
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
}
//STEP 6: Clean-up environment
rs.close();
stmt.close();
conn.close();
}catch(SQLException se){
//Handle errors for JDBC
se.printStackTrace();
}catch(Exception e){
//Handle errors for Class.forName
e.printStackTrace();
}finally{
//finally block used to close resources
try{
if(stmt!=null)
stmt.close();
}catch(SQLException se2){
}// nothing we can do
try{
if(conn!=null)
conn.close();
}catch(SQLException se){
se.printStackTrace();
}//end finally try
}//end try
System.out.println("Goodbye!");
}//end main
}//end JDBCExample
C:\>javac JDBCExample.java
C:\>
C:\>java JDBCExample
Connecting to database...
Creating statement...
Rows impacted : 1
ID: 100, Age: 18, First: Zara, Last: Ali
ID: 101, Age: 25, First: Mahnaz, Last: Fatma
ID: 102, Age: 35, First: Zaid, Last: Khan
ID: 103, Age: 30, First: Sumit, Last: Mittal
Goodbye!
C:\>
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 $$
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.
Parameter Description
OUT A parameter whose value is supplied by the SQL statement it returns. You
retrieve values from theOUT parameters with the getXXX() methods.
INOUT A parameter that provides both input and output values. You bind variables
with the setXXX() methods and retrieve values with the getXXX() methods.
The following code snippet shows how to employ the Connection.prepareCall() method to instantiate a
CallableStatement object based on the preceding stored procedure:
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.
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.
Example-
Following is the example which makes use of CallableStatement along with the following getEmpName()
MySQL stored procedure:
Make sure you have created this stored procedure in your EMP Database. You can use MySQL Query
Browser to get it done.
DELIMITER $$
This sample code has been written based on the environment and database setup done in previous chapters.
Copy and past following example in JDBCExample.java, compile and run as follows:
// Database credentials
static final String USER = "username";
static final String PASS = "password";
C:\>javac JDBCExample.java
C:\>
C:\>java JDBCExample
Connecting to database...
Creating statement...
Executing stored procedure...
Emp Name with ID:102 is Zaid
Goodbye!
C:\>
JDBC-Resultset
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:
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:
The first argument indicate the type of a ResultSet object and the second argument is one of two ResultSet
constants for specifying whether a result set is read-only or updatable.
Type of ResultSet:
The possible RSType are given below, If you do not specify any ResultSet type, you will automatically get
one that is TYPE_FORWARD_ONLY.
Type Description
ResultSet.TYPE_FORWARD_ONLY The cursor can only move forward in the result set.
ResultSet.TYPE_SCROLL_INSENSITIVE The cursor can scroll forwards and backwards, and the result
set is not sensitive to changes made by others to the
database that occur after the result set was created.
ResultSet.TYPE_SCROLL_SENSITIVE. The cursor can scroll forwards and backwards, and the result
set is sensitive to changes made by others to the database
that occur after the result set was created.
Concurrency of ResultSet:
The possible RSConcurrency are given below, If you do not specify any Concurrency type, you will
automatically get one that is CONCUR_READ_ONLY.
Concurrency Description
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 {
....
}
S.N
Methods & Description
.
Following is the example which makes use of few navigation methods described in Result Set tutorial.
This sample code has been written based on the environment and database setup done in previous chapters.
Copy and past following example in JDBCExample.java, compile and run as follows:
// Database credentials
static final String USER = "username";
static final String PASS = "password";
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
// Move cursor to the first row.
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
C:\>javac JDBCExample.java
C:\>
C:\>java JDBCExample
Connecting to database...
Creating statement...
Moving cursor to the last...
Displaying record...
ID: 103, Age: 30, First: Sumit, Last: Mittal
Moving cursor to the first row...
Displaying record...
ID: 100, Age: 18, First: Zara, Last: Ali
Moving cursor to the next row...
Displaying record...
ID: 101, Age: 25, First: Mahnaz, Last: Fatma
Goodbye!
C:\>
There is a get method for each of the possible data types, and each get method has two versions:
For example, if the column you are interested in viewing contains an int, you need to use one of the getInt()
methods of ResultSet:
S.N
Methods & Description
.
1 public int getInt(String columnName) throws SQLException
Returns the int in the current row in the column named columnName
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.
Following is the example which makes use of few getInt and getString methods described in Result Set
tutorial. This example is very similar to previous example explained in the Navigation Result Set Section.
This sample code has been written based on the environment and database setup done in previous chapters.
Copy and past following example in JDBCExample.java, compile and run as follows:
// Database credentials
static final String USER = "username";
static final String PASS = "password";
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
// Move cursor to the first row.
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
C:\>javac JDBCExample.java
C:\>
C:\>java JDBCExample
Connecting to database...
Creating statement...
Moving cursor to the last...
Displaying record...
ID: 103, Age: 30, First: Sumit, Last: Mittal
Moving cursor to the first row...
Displaying record...
ID: 100, Age: 18, First: Zara, Last: Ali
Moving cursor to the next row...
Displaying record...
ID: 101, Age: 25, First: Mahnaz, Last: Fatma
Goodbye!
C:\>
As with the get methods, there are two update methods for each data type:
1. One that takes in a column name.
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
.
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
.
It should be noted that tables you are working on should have Primary Key set properly.
This sample code has been written based on the environment and database setup done in previous chapters.
Copy and past following example in JDBCExample.java, compile and run as follows:
// Database credentials
static final String USER = "username";
static final String PASS = "password";
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
//Delete row
rs.deleteRow();
System.out.println("List result set after \
deleting one records...");
printRs(rs);
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
}
System.out.println();
}//end printRs()
}//end JDBCExample
C:\>javac JDBCExample.java
C:\>
C:\>java JDBCExample
Connecting to database...
Creating statement...
List result set for reference....
ID: 100, Age: 33, First: Zara, Last: Ali
ID: 101, Age: 40, First: Mahnaz, Last: Fatma
ID: 102, Age: 50, First: Zaid, Last: Khan
ID: 103, Age: 45, First: Sumit, Last: Mittal
Goodbye!
C:\>
JDBC-DataType
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.
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
Following examples shows how the Date and Time classes format standard Java date and time values to
match the SQL data type requirements.
import java.sql.Date;
import java.sql.Time;
import java.sql.Timestamp;
import java.util.*;
C:\>javac SqlDateTime.java
C:\>
C:\>java SqlDateTime
The Java Date is:Tue Aug 18 13:46:02 GMT+04:00 2009
The SQL DATE is: 2009-08-18
The SQL TIME is: 13:46:02
The SQL TIMESTAMP is: 2009-08-18 13:46:02.828
C:\>
JDBC-Transaction
If your JDBC Connection is in auto-commit mode, which it is by default, then every SQL statement is
committed to the database upon its completion.
That may be fine for simple applications, but there are three reasons why you may want to turn off auto-
commit and manage your own transactions:
1. To increase performance
2. To maintain the integrity of business processes
3. To use distributed transactions
Transactions enable you to control if, and when, changes are applied to the database. It treats a single SQL
statement or a group of SQL statements as one logical unit, and if any statement fails, the whole transaction
fails.
To enable manual- transaction support instead of the auto-commit mode that the JDBC driver uses by
default, use the Connection object's setAutoCommit() method. If you pass a boolean false to
setAutoCommit( ), you turn off auto-commit. You can pass a boolean true to turn it back on again.
For example, if you have a Connection object named conn, code the following to turn off auto-commit:
conn.setAutoCommit(false);
conn.commit( );
Otherwise, to roll back updates to the database made using the Connection named conn, use the following
code:
conn.rollback( );
The following example illustrates the use of a commit and rollback object:
try{
//Assume a valid connection object conn
conn.setAutoCommit(false);
Statement stmt = conn.createStatement();
In this case none of the abobe INSERT statement would success and everything would be rolled back.
Following is the example which makes use of commit and rollback described in Transaction tutorial.
This sample code has been written based on the environment and database setup done in previous chapters.
Copy and past following example in JDBCExample.java, compile and run as follows:
// Database credentials
static final String USER = "username";
static final String PASS = "password";
}catch(Exception e){
//Handle errors for Class.forName
e.printStackTrace();
}finally{
//finally block used to close resources
try{
if(stmt!=null)
stmt.close();
}catch(SQLException se2){
}// nothing we can do
try{
if(conn!=null)
conn.close();
}catch(SQLException se){
se.printStackTrace();
}//end finally try
}//end try
System.out.println("Goodbye!");
}//end main
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
}
System.out.println();
}//end printRs()
}//end JDBCExample
C:\>javac JDBCExample.java
C:\>
C:\>java JDBCExample
Connecting to database...
Creating statement...
Inserting one row....
Commiting data here....
List result set for reference....
ID: 100, Age: 18, First: Zara, Last: Ali
ID: 101, Age: 25, First: Mahnaz, Last: Fatma
ID: 102, Age: 30, First: Zaid, Last: Khan
ID: 103, Age: 28, First: Sumit, Last: Mittal
ID: 106, Age: 20, First: Rita, Last: Tez
ID: 107, Age: 22, First: Sita, Last: Singh
Goodbye!
C:\>
Using Savepoints:
The new JDBC 3.0 Savepoint interface gives you additional transactional control. Most modern DBMS
support savepoints within their environments such as Oracle's PL/SQL.
When you set a savepoint you define a logical rollback point within a transaction. If an error occurs past a
savepoint, you can use the rollback method to undo either all the changes or only the changes made after
the savepoint.
The Connection object has two new methods that help you manage savepoints:
There is one rollback ( String savepointName ) method which rolls back work to the specified savepoint.
try{
//Assume a valid connection object conn
conn.setAutoCommit(false);
Statement stmt = conn.createStatement();
//set a Savepoint
Savepoint savepoint1 = conn.setSavepoint("Savepoint1");
String SQL = "INSERT INTO Employees " +
"VALUES (106, 20, 'Rita', 'Tez')";
stmt.executeUpdate(SQL);
//Submit a malformed SQL statement that breaks
String SQL = "INSERTED IN Employees " +
"VALUES (107, 22, 'Sita', 'Tez')";
stmt.executeUpdate(SQL);
// If there is no error, commit the changes.
conn.commit();
}catch(SQLException se){
// If there is any error.
conn.rollback(savepoint1);
}
In this case none of the abobe INSERT statement would success and everything would be rolled back.
Following is the example which makes use of setSavepoint and rollback described in Transaction tutorial.
This sample code has been written based on the environment and database setup done in previous chapters.
Copy and past following example in JDBCExample.java, compile and run as follows:
// Database credentials
static final String USER = "username";
static final String PASS = "password";
}catch(Exception e){
//Handle errors for Class.forName
e.printStackTrace();
}finally{
//finally block used to close resources
try{
if(stmt!=null)
stmt.close();
}catch(SQLException se2){
}// nothing we can do
try{
if(conn!=null)
conn.close();
}catch(SQLException se){
se.printStackTrace();
}//end finally try
}//end try
System.out.println("Goodbye!");
}//end main
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
}
System.out.println();
}//end printRs()
}//end JDBCExample
C:\>javac JDBCExample.java
C:\>
C:\>java JDBCExample
Connecting to database...
Creating statement...
List result set for reference....
ID: 95, Age: 20, First: Sima, Last: Chug
ID: 100, Age: 18, First: Zara, Last: Ali
ID: 101, Age: 25, First: Mahnaz, Last: Fatma
ID: 102, Age: 30, First: Zaid, Last: Khan
ID: 103, Age: 30, First: Sumit, Last: Mittal
ID: 110, Age: 20, First: Sima, Last: Chug
Deleting row....
Deleting row....
List result set for reference....
ID: 100, Age: 18, First: Zara, Last: Ali
ID: 101, Age: 25, First: Mahnaz, Last: Fatma
ID: 102, Age: 30, First: Zaid, Last: Khan
ID: 103, Age: 30, First: Sumit, Last: Mittal
ID: 110, Age: 20, First: Sima, Last: Chug
Goodbye!
C:\>
JDBC-Exception
Exception handling allows you to handle exceptional conditions such as program-defined errors in a
controlled fashion.
When an exception condition occurs, an exception is thrown. The term thrown means that current program
execution stops, and control is redirected to the nearest applicable catch clause. If no applicable catch
clause exists, then the program's execution ends.
JDBC Exception handling is very similar to Java Excpetion handling but for JDBC, the most common
exception you'll deal with is java.sql.SQLException.
SQLException Methods:
A SQLException can occur both in the driver and the database. When such an exception occurs, an object of
type SQLException will be passed to the catch clause.
The passed SQLException object has the following methods available for retrieving additional information
about the exception:
Method Description
getMessage( ) Gets the JDBC driver's error message for an error handled by
the driver or gets the Oracle error number and message for a
database error.
getSQLState( ) Gets the XOPEN SQLstate string. For a JDBC driver error, no
useful information is returned from this method. For a
database error, the five-digit XOPEN SQLstate code is
returned. This method can return null.
getNextException( ) Gets the next Exception object in the exception chain.
printStackTrace(PrintStream s) Prints this throwable and its backtrace to the print stream
you specify.
printStackTrace(PrintWriter w) Prints this throwable and its backtrace to the print writer you
specify.
By utilizing the information available from the Exception object, you can catch an exception and continue
your program appropriately. Here is the general form of a try block:
try {
// Your risky code goes between these curly braces!!!
}
catch(Exception ex) {
// Your exception handling code goes between these
// curly braces, similar to the exception clause
// in a PL/SQL block.
}
finally {
// Your must-always-be-executed code goes between these
// curly braces. Like closing database connection.
}
Example:
Study the following example code to understand the usage of try....catch...finally blocks.
// Database credentials
static final String USER = "username";
static final String PASS = "password";
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
}
//STEP 6: Clean-up environment
rs.close();
stmt.close();
conn.close();
}catch(SQLException se){
//Handle errors for JDBC
se.printStackTrace();
}catch(Exception e){
//Handle errors for Class.forName
e.printStackTrace();
}finally{
//finally block used to close resources
try{
if(conn!=null)
conn.close();
}catch(SQLException se){
se.printStackTrace();
}//end finally try
}//end try
System.out.println("Goodbye!");
}//end main
}//end JDBCExample
C:\>javac JDBCExample.java
C:\>
When you run JDBCExample, it produces following result if there is no problem, otherwise corresponding
error would be caught and error message would be displayed:
C:\>java JDBCExample
Connecting to database...
Creating statement...
ID: 100, Age: 18, First: Zara, Last: Ali
ID: 101, Age: 25, First: Mahnaz, Last: Fatma
ID: 102, Age: 30, First: Zaid, Last: Khan
ID: 103, Age: 28, First: Sumit, Last: Mittal
C:\>
Try above example by passing wrong database name or wrong username or password and check the result.
JDBC-Batch Processing
Batch Processing allows you to group related SQL statements into a batch and submit them with one call to
the database.
When you send several SQL statements to the database at once, you reduce the amount of communication
overhead, thereby improving performance.
JDBC drivers are not required to support this feature. You should use the
DatabaseMetaData.supportsBatchUpdates() method to determine if the target database supports
batch update processing. The method returns true if your JDBC driver supports this feature.
The executeBatch() returns an array of integers, and each element of the array represents the
update count for the respective update statement.
Just as you can add statements to a batch for processing, you can remove them with the
clearBatch() method. This method removes all the statements you added with the addBatch()
method. However, you cannot selectively choose which statement to remove.
3. Add as many as SQL statements you like into batch using addBatch() method on created statement
object.
4. Execute all the SQL statements using executeBatch() method on created statement object.
Example:
The following code snippet provides an example of a batch update using Statement object:
Here is a typical sequence of steps to use Batch Processing with Statment Object:
This sample code has been written based on the environment and database setup done in previous chapters.
Copy and past following example in JDBCExample.java, compile and run as follows:
// Database credentials
static final String USER = "username";
static final String PASS = "password";
// Open a connection
System.out.println("Connecting to database...");
conn = DriverManager.getConnection(DB_URL,USER,PASS);
// Create statement
System.out.println("Creating statement...");
stmt = conn.createStatement();
// Clean-up environment
stmt.close();
conn.close();
}catch(SQLException se){
//Handle errors for JDBC
se.printStackTrace();
}catch(Exception e){
//Handle errors for Class.forName
e.printStackTrace();
}finally{
//finally block used to close resources
try{
if(stmt!=null)
stmt.close();
}catch(SQLException se2){
}// nothing we can do
try{
if(conn!=null)
conn.close();
}catch(SQLException se){
se.printStackTrace();
}//end finally try
}//end try
System.out.println("Goodbye!");
}//end main
while(rs.next()){
//Retrieve by column name
int id = rs.getInt("id");
int age = rs.getInt("age");
String first = rs.getString("first");
String last = rs.getString("last");
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
}
System.out.println();
rs.close();
}//end printRows()
}//end JDBCExample
C:\>javac JDBCExample.java
C:\>
C:\>java JDBCExample
Connecting to database...
Creating statement...
Displaying available rows...
ID: 95, Age: 20, First: Sima, Last: Chug
ID: 100, Age: 18, First: Zara, Last: Ali
ID: 101, Age: 25, First: Mahnaz, Last: Fatma
ID: 102, Age: 30, First: Zaid, Last: Khan
ID: 103, Age: 30, First: Sumit, Last: Mittal
ID: 110, Age: 20, First: Sima, Last: Chug
4. Add as many as SQL statements you like into batch using addBatch() method on created statement
object.
5. Execute all the SQL statements using executeBatch() method on created statement object.
The following code snippet provides an example of a batch update using PrepareStatement object:
Here is a typical sequence of steps to use Batch Processing with PrepareStatement Object:
This sample code has been written based on the environment and database setup done in previous chapters.
Copy and past following example in JDBCExample.java, compile and run as follows:
// Database credentials
static final String USER = "username";
static final String PASS = "password";
// Open a connection
System.out.println("Connecting to database...");
conn = DriverManager.getConnection(DB_URL,USER,PASS);
// Clean-up environment
stmt.close();
conn.close();
}catch(SQLException se){
//Handle errors for JDBC
se.printStackTrace();
}catch(Exception e){
//Handle errors for Class.forName
e.printStackTrace();
}finally{
//finally block used to close resources
try{
if(stmt!=null)
stmt.close();
}catch(SQLException se2){
}// nothing we can do
try{
if(conn!=null)
conn.close();
}catch(SQLException se){
se.printStackTrace();
}//end finally try
}//end try
System.out.println("Goodbye!");
}//end main
while(rs.next()){
//Retrieve by column name
int id = rs.getInt("id");
int age = rs.getInt("age");
String first = rs.getString("first");
String last = rs.getString("last");
//Display values
System.out.print("ID: " + id);
System.out.print(", Age: " + age);
System.out.print(", First: " + first);
System.out.println(", Last: " + last);
}
System.out.println();
rs.close();
}//end printRows()
}//end JDBCExample
C:\>javac JDBCExample.java
C:\>
C:\>java JDBCExample
Connecting to database...
Creating statement...
Displaying available rows...
ID: 95, Age: 20, First: Sima, Last: Chug
ID: 100, Age: 35, First: Zara, Last: Ali
ID: 101, Age: 25, First: Mahnaz, Last: Fatma
ID: 102, Age: 30, First: Zaid, Last: Khan
ID: 103, Age: 30, First: Sumit, Last: Mittal
ID: 110, Age: 20, First: Sima, Last: Chug
ID: 200, Age: 30, First: Zia, Last: Ali
ID: 201, Age: 35, First: Raj, Last: Kumar
JDBC-Stored Procedure
I have explained how to use Stored Procedures in JDBC while discussing JDBC - Statements. This tutorial
is similar to that section but it would give you additional information about JDBC SQL escape syntax.
Just as a Connection object creates the Statement and PreparedStatement objects, it also creates the
CallableStatement object which would be used to execute a call to a database stored procedure.
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 $$
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.
Parameter Description
INOUT A parameter that provides both input and output values. You bind variables
with the setXXX() methods and retrieve values with the getXXX() methods.
The following code snippet shows how to employ the Connection.prepareCall() method to instantiate a
CallableStatement object based on the preceding stored procedure:
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.
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.
Following is the example which makes use of CallableStatement along with the following getEmpName()
MySQL stored procedure:
Make sure you have created this stored procedure in your EMP Database. You can use MySQL Query
Browser to get it done.
DELIMITER $$
DELIMITER ;
This sample code has been written based on the environment and database setup done in previous chapters.
Copy and past following example in JDBCExample.java, compile and run as follows:
// Database credentials
static final String USER = "username";
static final String PASS = "password";
C:\>javac JDBCExample.java
C:\>
C:\>java JDBCExample
Connecting to database...
Creating statement...
Executing stored procedure...
Emp Name with ID:102 is Zaid
Goodbye!
C:\>
{keyword 'parameters'}
Here are following escape sequences which you would find very useful while doing JDBC programming:
d, t, ts Keywords:
They help identify date, time, and timestamp literals. As you know, no two DBMSs represent time and date
the same way. This escape syntax tells the driver to render the date or time in the target database's format.
For Example:
{d 'yyyy-mm-dd'}
Where yyyy = year, mm = month; dd = date. Using this syntax {d '2009-09-03'} is March 9, 2009.
stmt.executeUpdate(sql);
Similarly, you can use one of the following two syntaxes, either t or ts:
{t 'hh:mm:ss'}
Where hh = hour; mm = minute; ss = second. Using this syntax {t '13:30:29'} is 1:30:29 PM.
This is combined syntax of the above two syntax for 'd' and 't' to represent timestamp.
escape Keyword:
This keyword identifies the escape character used in LIKE clauses. Useful when using the SQL wildcard %,
which matches zero or more characters. For example:
If you use the backslash character (\) as the escape character, you also have to use two backslash
characters in your Java String literal, because the backslash is also a Java escape character.
fn Keyword:
This keyword represents scalar functions used in a DBMS. For example, you can use SQL function length to
ge the length of a string:
This returns 11, the length of the character string 'Hello World'.
call Keyword:
This keywork is used to call stored procedures. For example, for a stored procedure requiring an IN
parameter, use following syntax:
{call my_procedure(?)};
For a stored procedure requiring an IN parameter and returning an OUT parameter, use following syntax:
{? = call my_procedure(?)};
oj Keyword:
{oj outer-join}
JDBC-Streaming Data
A PreparedStatement object has the ability to use input and output streams to supply parameter data. This
enables you to place entire files into database columns that can hold large values, such as CLOB and BLOB
data types.
The setXXXStream() method requires an extra parameter, the file size, besides the parameter placeholder.
This parameter informs the driver how much data should be sent to the database using the stream.
Example
Consider we want to upload an XML file XML_Data.xml into a database table. Here is the content of this XML
file:
<?xml version="1.0"?>
<Employee>
<id>100</id>
<first>Zara</first>
<last>Ali</last>
<Salary>10000</Salary>
<Dob>18-08-1978</Dob>
<Employee>
Keep this XML file in the same directory where you are going to run this example.
This example would create a database table XML_Data and then file XML_Data.xml would be uploaded into
this table.
Copy and past following example in JDBCExample.java, compile and run as follows:
// Database credentials
static final String USER = "username";
static final String PASS = "password";
// Open a connection
System.out.println("Connecting to database...");
conn = DriverManager.getConnection(DB_URL,USER,PASS);
//Open a FileInputStream
File f = new File("XML_Data.xml");
long fileLength = f.length();
FileInputStream fis = new FileInputStream(f);
C:\>javac JDBCExample.java
C:\>
C:\>java JDBCExample
Connecting to database...
Creating XML_Data table...
<?xml version="1.0"?>
<Employee>
<id>100</id>
<first>Zara</first>
<last>Ali</last>
<Salary>10000</Salary>
<Dob>18-08-1978</Dob>
<Employee>
Goodbye!
C:\>