> On Tue, 2002-06-18 at 13:57, Umaa Rebbapragada wrote: > > DBD::Sybase > > That's what I figured :-) > > Well - DBI doesn't support multiple result sets internally. > > Maybe I'll have to add an ad-hoc version of the fetchall_*() routines, > or include some documentation regarding the limitations of using them > with multiple result sets. > > For now I think you'll either have to code your own subroutine that > fetches all the rows, or split the request in two parts. >
Rats ;) All right, thanks for the help. ps. Regarding the use of the UNION in my sql statement, that actually won't work in my case. For what I'm doing, I'm executing a stored proc, doing some inserts, and then a select statement. But since my stored proc has a return value, my result set contains only that value, and not the result from my select, which is what I really need. But, thanks for the suggestion though. > > > > -----Original Message----- > > > From: Michael Peppler [mailto:[EMAIL PROTECTED]] > > > Sent: Tuesday, June 18, 2002 1:51 PM > > > To: '[EMAIL PROTECTED]' > > > Subject: Re: fetchall_arrayref() and multiple result sets > > > > > > > > > On Tue, 2002-06-18 at 13:34, Umaa Rebbapragada wrote: > > > > I'm noticing that the fetchall_arrayref method in DBI > > > doesn't handle multple result sets. For example, if I > > > prepare a statement using this sql (for example): > > > > > > > > select * from A > > > > select * from B > > > > > > > > , execute this in DBI under a single statement handle, then > > > call Data::Dumper on fetchall_arrayref, it only returns the > > > result of the first query. Why not the second query too? > > > I'd rather not set up multiple statement handles, so if > > > there's a way to accomplish this with one, I'd be extremely > > > interested. > > > > > > > > > > Which DBD driver are you using? > > > > > > Michael > > > -- > > > Michael Peppler / [EMAIL PROTECTED] / http://www.mbay.net/~mpeppler > > [EMAIL PROTECTED] / ZetaTools, Inc / http://www.zetatools.com > > ZetaTools: Call perl functions as Sybase stored procedures! > > -- Michael Peppler / [EMAIL PROTECTED] / http://www.mbay.net/~mpeppler [EMAIL PROTECTED] / ZetaTools, Inc / http://www.zetatools.com ZetaTools: Call perl functions as Sybase stored procedures!
