Skip Menu |

This queue is for tickets about the DBD-AnyData CPAN distribution.

Report information
The Basics
Id: 7823
Status: new
Priority: 0/
Queue: DBD-AnyData

People
Owner: Nobody in particular
Requestors: Dan [...] DWright.Org
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 0.08
Fixed in: (no value)



Subject: DBD::AnyData has problems importing from DBI handles.
It turns out that under certain circumstances, when you doing an "ad_import" from a DBI handle, DBD::AnyData will try to stringify the reference to the DBI handle and use it as a literal file name. I sent this patch to the author on 7/7/04, but have not heard anything back: Date: Wed, 7 Jul 2004 22:02:39 -0400 (EDT) To: Jeff Zucker <jeff@vpservices.com> Subject: Something strange going on with AnyData.pm -- Solution?? Follow up... I think I found the problem. See below for a patch to apply against Version 0.08 of DBD::AnyData (AnyData.pm) -Dan 304a305,311 Show quoted text
> > my $dbh2 = $dbh; # Patch from Dan Wright - DWRIGHT@CPAN.ORG > if ( $format eq 'DBI' ) { # > $dbh2 = $file_name; # > $file_name = ''; # Prevent accidental storage of db handle later! > } # >
321,323c328 < } < my $dbh2 = $dbh; < $dbh2 = $file_name if $format eq 'DBI'; --- Show quoted text
> }
I've recently discovered that this bug is 100% reproducable whenever you attempt to import a table with zero rows.