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});
}
}
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.