Perl DBD

[gwise]

I have this multi-threaded perl program where I'm trying to do
independant database operations in separate threads. I was getting an
error similar to the following:

DB2 has no driver CLONE() function so is unsafe threaded

After looking at the code and some other perl DB drivers, I added the
following bit to the DB2.pm file:

sub CLONE {
$drh = undef;
}

I e-mailed a guy at IBM who had something to do with the Perl stuff
(sorry, can't remember the name) and he said that the underlying driver
should be all thread safe and this should work.
In all my testing that I've run, I've never had a problem running
multi-threaded with this code in place. So, my question is, does
anyone know how we'd get this change made to the DB2 DBD driver? I
gotta believe someone out there wants to use DB2 in a multi-threaded
Perl application. Am I going to have to keep patching this in by hand?

Thanks,
Greig Wise
Lead Database Developer
Press Ganey Associates

[Jan Nelken]

gw***@pressganey.com wrote:

I e-mailed a guy at IBM who had something to do with the Perl stuff
(sorry, can't remember the name) and he said that the underlying driver
should be all thread safe and this should work.
In all my testing that I've run, I've never had a problem running
multi-threaded with this code in place. So, my question is, does
anyone know how we'd get this change made to the DB2 DBD driver?

I have asked "a guy at IBM who had something to do with the Perl" and I will
report here any replies.

Jan M. Nelken

[Jan Nelken]

gw***@pressganey.com wrote:

So, my question is, does anyone know how we'd get this change made to the DB2 DBD driver?

I received this reply from maintainers of DBD::DB2 driver:

"Thanks for recommending this change. We agree that this is an important
functionality to have and your suggested change seems correct.
(http://search.cpan.org/~timb/DBI/lib...al_subroutine).
We own the DBD::DB2 database driver and we will ensure that this goes in the
next release. We welcome any further inputs from you that will help us in
improving the database driver."

Jan M. Nelken