RE: Stored procedures that return multiple rows

[James Turner]

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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Paul Baumgartel Sent: Thursday, August 23, 2001 4:11 PM To: Multiple recipients of list ORACLE-L Subject: 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 [EMAIL PROTECTED]