It's also available in DBD::ODBC (for ODBC drivers that support it)
using the driver-specific attribute odbc_more_results.  It may not be
in the docs for DBD::ODBC yet, though.  If you're connecting to DB2 on
a Win32 box, this may work if DBD::DB2 doesn't support it (assuming DB2
itself supports multiple result sets).

On Mon, May 14, 2001 at 09:12:01AM -0700, Michael Peppler <[EMAIL PROTECTED]> wrote:
> DBD::Sybase implements multiple result sets with a driver-specific
> attribute (syb_more_results). Maybe DB2 has the same thing?
> 
> Michael
> 
> Sterin, Ilya writes:
>  > Not sure what you mean exactly, but you can very easily do this
>  > programmatically having all the data in your fetch() and you can loop inside
>  > a loop as many times as you want.
>  > If you mean that when something is returned by a query, you want to loop
>  > through the rows, you easily accomplish this with execute()/fetch* methods.
>  > 
>  > Sorry if I didn't understand your exact inteded question.
>  > 
>  > Ilya Sterin
>  > 
>  > -----Original Message-----
>  > From: Keith E. Junker
>  > To: [EMAIL PROTECTED]
>  > Sent: 05/14/2001 10:04 AM
>  > Subject: Multiple result sets supported in DBI?
>  > 
>  > Everyone on my project is so thrilled that we can now run Stored
>  > Procedures in our DB2 database using Perl; however, we can't seem to
>  > find the DBI language to pull off something like:
>  > 
>  > while (result set) {
>  >  while (row in result set) {
>  >   do something . . .
>  >  }
>  > }
>  > 
>  > which is a usual RDBMS operation on results.
>  > 
>  > _Programming the Perl DBI_ does not mention multiple result sets. Is
>  > this a tacit admission that such capability is not (yet) a part of DBI?
>  > Did I miss an explicit such admission somewhere?
>  > 
>  > Keith Junker
> 
> -- 
> Michael Peppler - Data Migrations Inc. - [EMAIL PROTECTED]
> http://www.mbay.net/~mpeppler - [EMAIL PROTECTED]
> International Sybase User Group - http://www.isug.com
> Sybase on Linux mailing list: [EMAIL PROTECTED]

-- 
David Good                                         [EMAIL PROTECTED]

                 This space intentionally left blank.

Reply via email to