Roger,
My work with DBD-ADO and stored procedures is very limited. If you could
provide me with a few (at least one) complete example that generates this
error, fixing it would be much easier. Also, I haven't a lot of time to
work on DBD-ADO.
I do recall the bind interface (also with parameter support) is a little
tricky. A quick review of the 09bind.t tests, they look like the original
tests I grabbed from DBD::ODBC and DBD::Oracle.
I know calling a sp is database dependent ... Oracle uses begin; sp_call;
end; Where as PostgreSQL uses select sp_call;
Tom
On Wed, Oct 09, 2002 at 02:30:23PM +0200, Roger Perttu wrote:
> Roger Perttu wrote:
>
> > I've just started to experiment with DBD-ADO 2.5. I'm trying to figure
> > out if it's a viable option to DBD-ODBC.
> >
> > I've got this snippet of code that doesn't seem to work with DBD-ADO:
> >
> > my $dbh = newDbh();
> > my $sth = $dbh->prepare("{call testPrc(?)}");
> > $sth->bind_param(1, 10, { TYPE => 4 });
> > $sth->execute();
> > print '$sth->{NUM_OF_FIELDS}: ', $sth->{NUM_OF_FIELDS}, "\n";
> > if($sth->{NUM_OF_FIELDS})
> > { $sth->fetchrow_hashref('NAME');
> > }
> >
> >
> > Using SQL Profiler I can see that the code executes as it's supposed
> > to on the server.
> >
> > Finally my questions:
> >
> > 1. Why do I get those errors?
Not sure at the moment.
> > 2. Is DBD-ADO mature? Experiences?
Limited ...
> > 3. Does DBD-ADO support input/output parameters for stored procedures?
No or at least I doubt it.
> > Multiple result sets?
No.
> > 4. I've noticed that DBD-ADO call sp_sproc_columns for my sp's, can
> > that be avoided?
This looks like something the ADO driver is using. There isn't any
sp_sproc_columns in the DBD::ADO code that I know of.
--
Thomas A. Lowery
See DBI/FAQ http://xmlproj.dyndns.org/cgi-bin/fom
