I'm not quite sure what you mean by "proactively", but this deals with the case of no rows found ...
my $dbh = DBI->connect($conn_string, $user, $password,
{
RaiseError => 1,
}) || die $DBI::errstr;
my $sth = $dbh->prepare(<<__END_SQL__);
SELECT stuff
FROM some_place
WHERE some_condition = 1
__END_SQL__
$sth->execute;
my $num_rows = 0;
while (my @x = $sth->fetchrow)
{
$num_rows++;
do_something_with(@x);
}
die "No rows found\n" unless $num_rows;
print "Done\n";
------
We are the carpenters and bricklayers of the Information Age.
The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6
... strings and arrays will suffice. As they are easily available as native data types in any sane language, ... - blokhead, speaking on evolutionary algorithms
Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.
-
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.
|