Re: DBI 1.3.7->1.4.5

I'd start by looking at the Database.pm module, which appears to be something that is local to your installation.

You could add a $SIG{__WARN__} handler to print out a perl stack trace when the warnings occur to see if that gives you more information - something like:

use Carp qw(cluck);

$SIG{__WARN__} = sub { cluck(@_); }

... rest of code...
[download]

You can also enable DBI tracing (DBI->trace(3)) to see what calls are being made around the location of the warnings.

Michael

Comment on Re: DBI 1.3.7->1.4.5 Download Code

Replies are listed 'Best First'.
Re^2: DBI 1.3.7->1.4.5 by Anonymous Monk on Nov 12, 2004 at 16:40 UTC
But my code is done according to the docs. I cant see whats wrong with the selectall_hashref	[reply]
Re^3: DBI 1.3.7->1.4.5 by mpeppler (Vicar) on Nov 12, 2004 at 16:44 UTC
I don't really know what might be wrong - I haven't used DBD::ASAny. But what you need right now is more information - and the steps I suggested are one way of getting that. Michael	[reply]