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
    }
[download]

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...

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.