RE: Stored procedures that return multiple rows

On my previous gig all DB access was via stored procedures returning ref cursors through JDBC. The Java dweebs could do just about anything with the ref cursor. It worked really well. I could actually tune SQL queries on the running production application without any recompilation. Nice seperation of code. The DBA can tune real SQL code and the developers won't even know. No embedded SQL. Yeah!!
 

OCI can also accommodate ref cursors.

 

Steve Orr
 

  <FONT
  face=Tahoma>-----Original Message-----From: Paul Baumgartel   [mailto:pbaumgartel_at_mortgagesight.com]Sent: Thursday, August 23,   2001 2:11 PMTo: Multiple recipients of list   ORACLE-LSubject: Stored procedures that return multiple   rows
  We're considering a
  mandate that all database access be via stored procedures (probably in   packages).  These would be called either via OCCI (the C++ call   interface) or JDBC.  My question is whether anyone's had experience   in returning a result set from a PL/SQL procedure under   these circumstances, and how it was implemented:  did you   return a ref cursor, an index-by table, a set of arrays....?  Any advice   will be appreciated.  Thanks!
   
  Paul Baumgartel MortgageSight
  Holdings, LLC pbaumgartel_at_mortgagesight.com   

  <BLOCKQUOTE dir=ltr
style="MARGIN-RIGHT: 0px">  Received on Thu Aug 23 2001 - 15:27:07 CDT