I’m running Win XP with Perl 5.8.8.
If I try and run the following code :
use DBI;
my %drivers = DBI->installed_drivers();
foreach (keys( %drivers)) {
print "$_ uses $drivers{$_}\n";
}
Nothing is returned. Yet if I use :
my @drivers = DBI->available_drivers();
I
On 7/17/06, Ephraim Dan <[EMAIL PROTECTED]> wrote:
Can someone else try to reproduce a memory leak in a simple
connect/prepare/execute/disconnect loop using DBI 1.51 and any DBD driver?
I created a test program using the test harness distributed with
DBD::Informix and found a small but gentl
Hi,
I built DBD::Oracle 1.17 on a RHEL AS4 machine using the Instant Client
libraries. I can use it and DBI 1.48 quite successfully to connect to our
Oracle 10 server via CGI or command-line perl.
The same code, however, segfaults with the stack trace attached below when
run in a mod_perl envir
You will have to update DBI and DBD::Oracle from ActiveState. The only
problem I see is the version of DBD::Oracle 1.17 will only work for a
limited numer of Oracle clients ( Instantclient 10.2.0.1 and I think 10XE.)
and windos OSes.
You will have to download that client from Oracle and use
I was using Perl 5.6.x (ActiveState Windows port) to connect to Oracle
9i. The modules used then were DBI 1.48 and DBD-Oracle 1.16. I have now
upgraded to Perl 5.8.8 with DBI 1.50 and DBD-Oracle 1.17. The upgrade
was necessitated by the WWW::Babelfish module. Now while I'm able to use
Babelfis
Yes we have seen that one before there is an
open bug report for it here
http://rt.cpan.org/Public/Bug/Display.html?id=18012
can you fill in the rest of this table for
me
Perl: 5.8.8DBI: 1.5.1DBD::Oracle:
1.17OS: ?Oracle server: ?Oracle client: ?Oracle database
c
I am getting the following error when I am
trying to make test. The environment is Solaris 10 using PERL 5.8.8, DBI 1.51
and DBD 1.17.
t/24implicit_utf8...NOK 33# Failed test
'byte_string test of row 4: column: nch (uft8) smiley
face'# in t/nchar_test_lib.pl at line
341.#
It certainly does appear to leak memory for you, too. My script is similar, as
are my results.
Thanks for checking.
Appears to be a confirmed memory leak to me. Does anyone have an idea of how
the weakref code can be fixed to solve this? It appears that Tim doesn't have
time...
Thanks,
Eph
