Webmaster Forum / Perl / DBI Library / February 2004

Tim,
Would you mind if DBI held constants, exportable via sql_types for
SQL_CURSOR_XXXXX.  
I have a patch submitted to me for DBD::ODBC which allows multiple queries

CHANGES in DBI 1.41 said:
 Changed trace level to be a four bit integer (levels 0 thru 15)
   and a set of topic flags (no topics have been assigned yet).
CHANGES in DBI 1.42 will say:

If you set up an error handler with Sybase::DBlib::seterrhandle(),
and your error handler returns undef, then you get a strange message
'Use of uninitialized value in subroutine entry'.  It would be better
to print a more obvious warning about an undef return value from the

After initial setup by Rob and Ask at perl.org, and a kickstart
from Jeff Urlwin loading the old releases, I'm happy to say that
the DBD::Oracle source is now hosted at
    http://svn.perl.org/modules/dbd-oracle/trunk

I have converted DBI ( the latest svn trunk - #93 )
to use PERL_NO_GET_CONTEXT ( with pTHX_/aTHX_ added
where necessary ). The DBI test suite works fine,
an I have been using it w/o problems on my production

using DBI 1.40/1.41 there seems to be a small bug in the macro definition for the macro DBD_ATTRIB_DELETE(...)
The following patch should help.
493c493
<       hv_delete((HV*)attribs, key, len, G_DISCARD)

A second release candidate is available for testing at:
 http://homepage.eircom.net/~timbunce/DBI-1.41-rc2-20040222.tar.gz
=head1 CHANGES in DBI 1.41 (svn rev 130),    22nd February 2004
 Fixed execute_for_array() so tuple_status parameter is optional

New list member here with a sybperl question.
My shop has just upgraded our production and contingency servers to Sybase 12.5/Solaris 2.8 from 11.9.2/2.6.  With contingency just having been rebuilt, I am now in the process of testing our scripts to ensure they work should we need ...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
PostgreSQL has recently added a true server-side prepare, which
raises some issues in regards to the prepare/execute DBI model.

DBD::Pg 1.32_2 is out and ready for testing.  I uploaded it to CPAN on
Wednesday (EST)  so it should already be out on the CPAN mirrors.
Enjoy,
Rudy

I've been lurking through the $sth->{NAME} issues and it seems to me that
the current behavior of DBD::ODBC is onerous.  If dbd_describe() fails, it
croaks (which is what DBD::Oracle does).
If we return a Nullsv at this point, the end application does *not* get an

Hi Michael,
DBD::Sybase transparently opens a second connection to the database in order
to emulate multiple active sth's per dbh. That seems pretty reasonable to me,
but it foils Bugzilla's primitive table locking/transaction processing and

Tim,
This patch averts a small warning emitted when running Makefile.PL from the
current subversion repos. (Hey -- at least someone is using it!!!)
Also, I have a minor request.  When you release release candidates, I'd like

A release candidate is available for testing at:
 http://homepage.eircom.net/~timbunce/DBI-1.41-rc1-20040217.tar.gz
head1 CHANGES in DBI 1.41,    17th February 2004
 Fixed execute_for_array() so tuple_status parameter is optional

I'm working on database plugin for editor vim. I need print data fetched
from database to stdout. I write method DBI::st::dump_data(). This peace
of code follows. This code can be found (with little modification) also
on website: