File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes JDBC and Relational Databases and the fly likes Jdbc q Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Databases » JDBC and Relational Databases
Bookmark "Jdbc q" Watch "Jdbc q" New topic

Jdbc q

NileshJ Njadhav

Joined: Jan 18, 2011
Posts: 3
Difference between statement and prepare statement?
Mohamed Sanaulla
Saloon Keeper

Joined: Sep 08, 2007
Posts: 3151

NileshJ Njadhav wrote:Difference between statement and prepare statement?

Statement and PreparedStatement.

Mohamed Sanaulla | My Blog
NileshJ Njadhav

Joined: Jan 18, 2011
Posts: 3
Martin Vajsar

Joined: Aug 22, 2010
Posts: 3728

Sometimes people test the speed of a Statement vs. PreparedStatement and notice that if the Statement is executed only a handful of times, it is slightly faster, so they conclude the Statement is the way to go if you execute it less than, say, 10 times in your application. This is, of course, not a good idea because of SQL injection anyway, but even the performance perspective is wrong. If the application is actually used by many (say, 100) users and each user invokes the 10-statement functionality, the DB gets hit by these Statements thousand times, not ten times. Which means the load on the DB is much higher and the PrepareStatement would clearly win performance-wise.

I haven't ever seen a Statement/PreparedStatement performance comparison which would mention it, so I thought I'd point it out here.
I agree. Here's the link:
subject: Jdbc q
It's not a secret anymore!