I think the statement about "prepare(); loop { execute() }" being faster / more efficient than "loop { do() }" was meant to apply to this sort of comparison (untested):
use strict;
use DBI;
use Benchmark qw/timethese/;
my $times = shift;
my @vals = ( 10734..10845 );
my $sql = "UPDATE Tests SET foo = 'bar' WHERE ID = ?";
my $dbh = DBI->connect("connection_string...");
my $sth = $dbh->prepare( $sql );
sub dbi_do {
for my $val ( @vals ) {
(my $dosql = $sql) =~ s/\?/'$val'/;
$dbh->do( $dosql );
}
}
sub dbi_prep {
for my $val ( @vals ) {
$sth->execute( $val );
}
}
timethese( $times, {
DbiDo => \&dbi_do,
PrepExec => \&dbi_prep,
});
Of couse, that sort of demonstration also highlights a good reason, besides speed, for favoring the "prepare/execute" approach: using placeholders in the SQL statement tends to be better and easier than using quoted strings.
(updated to fix the "use Benchmark" line)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.