Re: callback function params

If you still can, consider using DBI together with DBD::SQLite instead. It is more commonly used and does not tie your application to SQLite.

Looking at the documentation of DB::SQLite, it seems that you are supposed to give it a callback like the following:

$db->select( $sql, sub {
    my ($sth) = @_;
    use Data::Dumper;
    print "I received the following statement handle: ";
    print Dumper $sth->fetchall_arrayref;
});
[download]

Update: Fixed syntax errors in code

Comment on Re: callback function params Download Code

Replies are listed 'Best First'.
Re^2: callback function params by azadian (Sexton) on May 26, 2024 at 14:14 UTC
Thanks for the suggestion. Personally, I'd prefer to avoid DBD::SQLite, as it provides gobs more functionality than I need. For additional information, when I invoke Dumper(@_) in my callback subroutine, I get: `$VAR1 = bless( {}, 'DBI::st' );` [download] When I try the proffered code, I get: Can't call method "fetchall_arrayref" on an undefined value.	[reply] [d/l]
Re^3: callback function params by soonix (Chancellor) on May 26, 2024 at 21:11 UTC
That looks like you omitted the `my ($sth) = @_;` line.	[reply] [d/l]
Re^3: callback function params by azadian (Sexton) on May 27, 2024 at 17:32 UTC
Ooops! Found my problem. I simply didn't have $date in quotes, as SQL requires. Thanks for the help.	[reply]
Re^4: callback function params by Fletch (Bishop) on May 28, 2024 at 11:11 UTC
Congratulations on the injection vulnerability; say hi to Bobby when he calls. Also you’re not avoiding DBI by using this module, you’re just adding a layer of 20 year old code over the top of the standard DB interface because it uses both it and DBD::SQLite. The cake is a lie. The cake is a lie. The cake is a lie.	[reply]