If you repeat this pattern, it tells you one things: You should write it into a subroutine.
sub first_row {
my ($dbh, $query, @args) = @_
my $sth = $dbh->prepare($query);
my $rv = $sth->execute(@args);
my $first_row = $sth->fetchrow_hashref;
return ($rv, $first_row);
}
my ($success, $first_result) = first_row($dbh, "SELECT ... ");
# and if you don't want to actually check success
my $second_result = first_row(...);
(Update: or as ikegami points out, just use $dbh->fetchrow_hashref($query) in the first place.)
(Even more elegant if you don't check for $rv, but instead die on errors, and catch them where appropriate).
If you insist on your current pattern, you can use warnings, but disable single warnings that bother you - read perllexwarn for more details. Or simply put a block around the declarations.
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.