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 Callable statement vs prepared statement Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Databases » JDBC and Relational Databases
Bookmark "Callable statement vs prepared statement" Watch "Callable statement vs prepared statement" New topic

Callable statement vs prepared statement

fahad siddiqui
Ranch Hand

Joined: Jun 14, 2006
Posts: 85
Callable is used to call stored procedures specifically.
We can call stored procedures using Prepared Statement also using sql string as
{call sp_name (?,?)}

Why should we choose one over the other? What are the advantages enjoyed?
Paul Sturrock

Joined: Apr 14, 2004
Posts: 10336

Not an ORM question. Moving...

JavaRanch FAQ HowToAskQuestionsOnJavaRanch
Jeanne Boyarsky
author & internet detective

Joined: May 26, 2003
Posts: 33132

Originally posted by fahad siddiqui:
Why should we choose one over the other? What are the advantages enjoyed?

If you have a stored procedure, you should use CallableStatement. A PreparedStatement is not guaranteed to work across all databases and drivers. This makes your code less robust. While you probably aren't changing databases with stored procs, you are likely to upgrade the driver.

Oracle fixed a bug in getDate() in Oracle 10 which caused legacy code to break that was relying on a side effect. If you follow the spec (or intent of the API), you protect your code against future changes.

[OCA 8 book] [Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
I agree. Here's the link:
subject: Callable statement vs prepared statement
jQuery in Action, 3rd edition