Skip to main content

PreparedStatement Interface

PreparedStatement interface

The PreparedStatement interface is a subinterface of Statement. It is used to execute parameterized query.

Let's see the example of parameterized query:

  1. String sql="insert into emp values(?,?,?)";  

As you can see, we are passing parameter (?) for the values. Its value will be set by calling the setter methods of PreparedStatement.

Why use PreparedStatement?

Improves performance: The performance of the application will be faster if you use PreparedStatement interface because query is compiled only once.


How to get the instance of PreparedStatement?

The prepareStatement() method of Connection interface is used to return the object of PreparedStatement. Syntax:

  1. public PreparedStatement prepareStatement(String query)throws SQLException{}  

Methods of PreparedStatement interface

The important methods of PreparedStatement interface are given below:

MethodDescription
public void setInt(int paramIndex, int value)sets the integer value to the given parameter index.
public void setString(int paramIndex, String value)sets the String value to the given parameter index.
public void setFloat(int paramIndex, float value)sets the float value to the given parameter index.
public void setDouble(int paramIndex, double value)sets the double value to the given parameter index.
public int executeUpdate()executes the query. It is used for create, drop, insert, update, delete etc.
public ResultSet executeQuery()executes the select query. It returns an instance of ResultSet.

Example of PreparedStatement interface that inserts the record

First of all create table as given below:

  1. create table emp(id number(10),name varchar2(50));  

Now insert records in this table by the code given below:

  1. import java.sql.*;  
  2. class InsertPrepared{  
  3. public static void main(String args[]){  
  4. try{  
  5. Class.forName("oracle.jdbc.driver.OracleDriver");  
  6.   
  7. Connection con=DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe","system","oracle");  
  8.   
  9. PreparedStatement stmt=con.prepareStatement("insert into Emp values(?,?)");  
  10. stmt.setInt(1,101);//1 specifies the first parameter in the query  
  11. stmt.setString(2,"Ratan");  
  12.   
  13. int i=stmt.executeUpdate();  
  14. System.out.println(i+" records inserted");  
  15.   
  16. con.close();  
  17.   
  18. }catch(Exception e){ System.out.println(e);}  
  19.   
  20. }  
  21. }  

Example of PreparedStatement interface that updates the record

  1. PreparedStatement stmt=con.prepareStatement("update emp set name=? where id=?");  
  2. stmt.setString(1,"Sonoo");//1 specifies the first parameter in the query i.e. name  
  3. stmt.setInt(2,101);  
  4.   
  5. int i=stmt.executeUpdate();  
  6. System.out.println(i+" records updated");  

Example of PreparedStatement interface that deletes the record

  1. PreparedStatement stmt=con.prepareStatement("delete from emp where id=?");  
  2. stmt.setInt(1,101);  
  3.   
  4. int i=stmt.executeUpdate();  
  5. System.out.println(i+" records deleted");  

Example of PreparedStatement interface that retrieve the records of a table

  1. PreparedStatement stmt=con.prepareStatement("select * from emp");  
  2. ResultSet rs=stmt.executeQuery();  
  3. while(rs.next()){  
  4. System.out.println(rs.getInt(1)+" "+rs.getString(2));  
  5. }  


Example of PreparedStatement to insert records until user press n

  1. import java.sql.*;  
  2. import java.io.*;  
  3. class RS{  
  4. public static void main(String args[])throws Exception{  
  5. Class.forName("oracle.jdbc.driver.OracleDriver");  
  6. Connection con=DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe","system","oracle");  
  7.   
  8. PreparedStatement ps=con.prepareStatement("insert into emp130 values(?,?,?)");  
  9.   
  10. BufferedReader br=new BufferedReader(new InputStreamReader(System.in));  
  11.   
  12. do{  
  13. System.out.println("enter id:");  
  14. int id=Integer.parseInt(br.readLine());  
  15. System.out.println("enter name:");  
  16. String name=br.readLine();  
  17. System.out.println("enter salary:");  
  18. float salary=Float.parseFloat(br.readLine());  
  19.   
  20. ps.setInt(1,id);  
  21. ps.setString(2,name);  
  22. ps.setFloat(3,salary);  
  23. int i=ps.executeUpdate();  
  24. System.out.println(i+" records affected");  
  25.   
  26. System.out.println("Do you want to continue: y/n");  
  27. String s=br.readLine();  
  28. if(s.startsWith("n")){  
  29. break;  
  30. }  
  31. }while(true);  
  32.   
  33. con.close();  
  34. }}  


Anurag Rana Educator CSE/IT

Comments

Popular posts from this blog

Standard and Formatted Input / Output in C++

The C++ standard libraries provide an extensive set of input/output capabilities which we will see in subsequent chapters. This chapter will discuss very basic and most common I/O operations required for C++ programming. C++ I/O occurs in streams, which are sequences of bytes. If bytes flow from a device like a keyboard, a disk drive, or a network connection etc. to main memory, this is called   input operation   and if bytes flow from main memory to a device like a display screen, a printer, a disk drive, or a network connection, etc., this is called   output operation . Standard Input and Output in C++ is done through the use of  streams . Streams are generic places to send or receive data. In C++, I/O is done through classes and objects defined in the header file  <iostream> .  iostream  stands for standard input-output stream. This header file contains definitions to objects like  cin ,  cout , etc. /O Library Header Files There are...

locking

DBMS Locking Part I (DBMS only) TECHNICAL ARTICLES -> PERFORMANCE ARTICLES [  Back  ] [  Next  ] DBMS is often criticized for excessive locking – resulting in poor database performance when sharing data among multiple concurrent processes. Is this criticism justified, or is DBMS being unfairly blamed for application design and implementation shortfalls? To evaluate this question, we need to understand more about DBMS locking protocols. In this article, we examine how, why, what and when DBMS locks and unlocks database resources. Future articles will address how to minimize the impact of database locking. THE NEED FOR LOCKING In an ideal concurrent environment, many processes can simultaneously access data in a DBMS database, each having the appearance that they have exclusive access to the database. In practice, this environment is closely approximated by careful use of locking protocols. Locking is necessary in a concurrent environment to as...

DATA WAREHOUSE VERSUS DATA MART: THE GREAT DEBATE

DATA WAREHOUSE VERSUS DATA MART: THE GREAT DEBATE Customers exploring the field of business intelligence for the first time often lead with: What is the difference between a data warehouse and a data mart? The next question follows as predictably as night follows day: which one does my company need? Let me start by saying that the two terms are often confused. Indeed, some people in the industry use them virtually interchangeably, which is unfortunate, because they do reflect a valuable hierarchical difference. The Data Warehouse A "data warehouse" will typically contain the full range of business intelligence available to a company from all sources. That data consists of transaction-processing records, corporate and marketing data, and other business operations information; for example, a bank might include loans, credit card statements, and demand deposits data, along with basic customer information. This internal data is frequently combined with statistica...