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 new features available in jdbc 4.0?
What is metadata in jdbc?
Explain the various types of locking system in jdbc?
What isolation level is used by the DBMS when inserting, updating and selecting rows from a database?
code to insert values/rows into oracle database from a java swing textfield when a button is pressed(using preparedstatements)
What is an advantage of using the jdbc connection pool?
What is odbc. how is it related to sql cli?
What are the advantages of database connection pooling?
Where can I find ojdbc14 jar file?
What is JDBC PreparedStatement?
What does the connection object represents?
Name the method, which is used to prepare a callablestatement.
Does jdbc use ssl?
How can I connect mysql or oracle with java?
What does jdbc do?