On Mon, 2004-05-03 at 05:45, Matthew O. Persico wrote:
> On Sat, 1 May 2004 18:53:30 +0100, Tim Bunce typed:
>
> > =head2 Example Implementation via DBI Subclass
> >
> > Another way to think about the behaviour of more_results() is to
> > imagine a DBI subclass that did something like this:
> >
> > sub prepare {
> > my ($dbh, $Statement) = @_;
> > my @statements = split /;/, $Statement; # split
> > statements
> > my $sth = $dbh->SUPER::prepare(shift @statements); # prepare the
> > first
> > $sth->{statements} = [EMAIL PROTECTED] # store the rest
> > if @statements;
> > return $sth;
> > }
> >
> From what I understand, I'm not sure this maps onto the likes of
> Sybase and MSSQL. From what I understand from reading (and I may be
> woefully wrong here) a ; would have to separate each sub-statement in
> a batch. A corresponding Sybase batch would look like:
>
> declare @foo int, @bar varchar
> ;
I think Tim is just providing a sample implementation, not required
behavior.
Certainly DBD::Sybase will continue to behave the way it does now, with
the possible exception of conforming to a few additional rules if they
make it into the DBI standard (such as skipping results that don't
return any rows, for example).
I still need to read the original post more carefully to make sure that
I understand and agree/see no problem with its various provisions,
though.
Michael
--
Michael Peppler Data Migrations, Inc.
[EMAIL PROTECTED] http://www.peppler.org/
Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short
or long term contract positions - http://www.peppler.org/resume.html
