|
|
Featured White Papers
- Why choose an Open Source BPM?
- 10 FAQs on Business Process Management
- Best Practices for Getting Started with BPM
- Free Your Devs From The Pain Of Java Redeploys
- Increase Velocity 40% by Using JRebel
- What Developers Want: The End of Application Redeploys
- Developer Productivity Report: Java Tools, Tech, Devs, and Data
- Coding with JRebel: Java Forever Changed
- Utilizing Fast Testing to Transform Java Development
- Do You Really Get Classloaders?
- Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
- Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
- Coding with JRebel, Java Forever Changed
- 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data
Sponsored Links
Sponsored Links
Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs
Server-side Java: Use JDBC for industrial-strength performance, Part 1
Java server-side data mining patterns made powerful with JDBC
Page 2 of 4
| Usage Scenario | Description | Diagram of Scenario |
|---|---|---|
ResultSet CallableStatement scenario
|
Create a CallableStatement from the open database Connection. Pass an SQL procedure call (executing a database stored procedure) to the CallableStatement and receive a ResultSet from the database.
|
ResultSet CallableStatement Scenario |
Table 3. The hybrid ResultSet CallableStatement scenario
Although the ResultSet CallableStatement scenario seems simple enough to realize in Java code, the differences between databases and JDBC database drivers are now
growing painfully visible to the developer. Despite the fact that JDBC is supposed to be mostly platform- and database-independent,
the specifics of each database are visible not only when defining a stored procedure, but also when trying to return a ResultSet from one. Some database engines cannot return values from stored procedures; values that should be returned to the Java application
must instead be declared as output parameters. Other databases may return only some kinds of types from a stored procedure
call (generally INTEGER values to indicate the error code status of a procedure call). There are still other database types that might be able to
return a full JDBC ResultSet equivalent (in some cases, this would correspond to a database CURSOR type), either as a result from a stored procedure call or as an output parameter. Depending on the capabilities of the stored
procedure execution engine being called, different calling methods may be used, as described in the table below:
- Feedback
More from JavaWorld
Resources
- jGuru FAQ page (see JDBC section)
http://www.jguru.com/portal/index.jsp?tab=3 - Sun's JDBC homepage
http://java.sun.com/products/jdbc/ - JavaWorld's Topical Index on JDBC
http://www.javaworld.com/javaworld/common/jw-ti-jdbc.html
Server-side Java: Read the whole series -archived on JavaWorld
- Welcome to the server-side Java series
- Understanding JavaServer Pages Model 2 Architecture
- Create forward-compatible beans in EJB, Part 1
- Create forward-compatible beans in EJB, Part 2
- Use JDBC for industrial-strength performance, Part 1
- Use JDBC for industrial-strength performance, Part 2
- Counting tiers - one, two, or n?
- Build distributed applications with Java and XML
- Internationalize JSP-based Websites
- Patterns for flexible initialization, Part 1
- Patterns for flexible initialization, Part 2
- Advanced form processing using JSP
- Using XML and JSP together