The stupid question is the question not asked | |
PerlMonks |
Re: DBD::AnyData completely broken (or is it just me?)by bmann (Priest) |
on Jun 29, 2005 at 07:49 UTC ( [id://470914]=note: print w/replies, xml ) | Need Help?? |
It's just you ;) (just kidding, it looks like a documentation bug at the very least.) Change the name of your table from 'import' to 'mytable', and it works. It isn't documented, but using 'import' as the table name causes SQL::Statement to try to call SQL::Statement::Functions::SQL_FUNCTION_IMPORT() with the wrong parameters - it expects a statement handle, which it doesn't get. Using the debugger, I verified that SQL_FUNCTION_IMPORT is not called wrongly when the table is named differently. Here's an example using ad_catalog (I get the same results with ad_import):
Results: I can't seem to suppress or fix the "DBI handle cleared whilst still active" message Hopefully, jZed can shed more light when he gets a chance. Update: I am using Debian unstable, all packages up-to-date
In Section
Seekers of Perl Wisdom
|
|