comment on

I would take trammell's suggestion a step further and also not recreate the statement handle every time and actually take advantage of the statement handle (and placeholders)-- i think this will have a decent improvement in the performance (amount of gain is probably db-dependent):


my $dbh = DBI->connect('DBI:mysql:diet', {RaiseError => 1, AutoCommit 
+=> 0} ) || die "Failed to connect: $DBI::errstr";
my $sth = $dbh->prepare( qq{select topic FROM table1 WHERE uri LIKE ?}
+ );

search($sth, 'foo');
search($sth, 'bar');

$sth->finish();
$dbh->disconnect(); #disconnect from database;

sub search{
  my $sth = shift;  # require statement handle (this could probably be
+ a global var instead if desired)
  my $q = shift;    # take search parameter from html <form/>
  my $found = 0; #initialize category found count;
  $sth->execute($q);
  my $rows = $sth->fetchall_arrayref( {} );
  printf "%d rows found for '%s'.\n", scalar(@$rows), $q;
  foreach my $row (@$rows){
    printf "   Topic: %s\n", &topic($row->{topic});
  }
}
[download]

In reply to Re^3: How to improve MYSQL search performance of perl? by davidrw
in thread How to improve MYSQL search performance of perl? by nan

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.


We don't bite newbies here... much
	PerlMonks