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 is two-phase commit in the database?
Is jdbc a middleware?
What do you mean by odbc?
What is an SQL Locator?
What is the meaning of batch updates?
What causes the "No suitable driver" error?
How do I insert/update records with some of the columns having NULL value?
What is an odbc driver?
What is a statement?
What is a java driver?
Once I have the Java 2 SDK, Standard Edition, from Sun, what else do I need to connect to a database?
What is meant by connection string?
What is jdbc resultsetmetadata interface?
List the advantages of using datasource?
What are the different types of locking in JDBC?
