Answer Posted / guest
There's a popular belief that using a PreparedStatement
object is faster than using a Statement object. After all, a
prepared statement has to verify its metadata against the
database only once, while a statement has to do it every
time. So how could it be any other way? Well, the truth of
the matter is that it takes about 65 iterations of a
prepared statement before its total time for execution
catches up with a statement. This has performance
implications for your application, and exploring these
issues is what this section is all about.
When it comes to which SQL statement object performs better
under typical use, a Statement or a PreparedStatement, the
truth is that the Statement object yields the best
performance. When you consider how SQL statements are
typically used in an application--1 or 2 here, maybe 10-20
(rarely more) per transaction--you realize that a Statement
object will perform them in less time than a
PreparedStatement object. In the next two sections, we'll
look at this performance issue with respect to both the OCI
driver and the Thin driver.
| Is This Answer Correct ? | 0 Yes | 8 No |
Post New Answer View All Answers
What are the advantages of using preparedstatement in java?
What are the different types of classes in the api component?
What are the common jdbc exceptions?
Write an sql to find all records having all upper case alphanumeric characters in a field ?
When do we get java.sql.SQLException: No suitable driver found?
Is jdbc open source?
What is the query used to display all tables names in SQL Server (Query analyzer)?
What is jdbc in dbms?
What are the three basic components of the odbc architecture?
How can you load the drivers?
What is the use of callablestatement? Name the method, which is used to prepare a callablestatement.
What is execute in java?
How to use JDBC API to call Stored Procedures?
Can I set up a connection pool with multiple user IDs? The single ID we are forced to use causes problems when debugging the DBMS.
What is jdbc odbc?