If you are using a database like
MySQL,
that doesn't support placeholders, your benchmark isn't really surprising
as DBI emulating it is probably no faster than a simple string concatenation.
What might be faster, is using bind_columns to save yourself some copying:
$sth->execute();
$sth->bind_columns(\my $id, \my $subject, \my $body,
\my $mailto, \my $mailfrom, \my $type);
while ($sth->fetch) {
# loop as before
}
What I'm interested in, but haven't had time to play with is the new
functionality added in DBI ver 1.30 (
docs)
for
fetchall_arrayref:
$tbl_ary_ref = $sth->fetchall_arrayref( $slice, $max_rows );
If $max_rows is defined and greater than or equal to zero then it is used to limit the number of rows fetched before returning. fetchall_arrayref() can then be called again to fetch more rows. This is especially useful when you need the better performance of fetchall_arrayref() but don't have enough memory to fetch and return all the rows in one go.
Hope this helps...
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.