Interested to Buy Any Domain ? << Click Here >> for more details...
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 connection pooling and why it is used?
What is database deadlock ? How can we avoid them?
How will you perform truncation using JDBC?
What are the jdbc drivers in java?
Which jdbc driver type s is are the jdbc odbc bridge?
How do I load a database driver with JDBC 4.0 / Java 6?
What is an odbc driver?
What is the role of jdbc drivermanager class?
What is the purpose of the jdbc resultset interface?
java based application for hospital management
What is JDBC Batch Processing and what are it’s benefits?
How to use JDBC to connect Microsoft Access?
Where is jdbc url mysql?
Why do we use jdbc statements?
Is jdbc a framework?
