From jturner@ungames.com Thu, 23 Aug 2001 13:21:13 -0700 From: "James Turner" Date: Thu, 23 Aug 2001 13:21:13 -0700 Subject: RE: Stored procedures that return multiple rows Message-ID: MIME-Version: 1.0 Content-Type: text/plain Paul,   Our applications do database access solely though packaged pl/sql calls which return a ref cursor.  Some use OCI, others JDBC.  Experience has been very positive.  Administrative advantages in having such an "abstraction layer" between apps and the database are manifold   As a DBA, you have a lot of leeway to change things around on the back end w/o breaking the app.  One drawback to the approach is that it requires more up-front planning on the app developers to identify the database calls.   James Turner DBA Unplugged Games -----Original Message-----From: root@fatcity.com [mailto:root@fatcity.com]On Behalf Of Paul BaumgartelSent: Thursday, August 23, 2001 4: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@mortgagesight.com