I usually use a callback routine for convenience.
This reduces looping logic to one common place.
sub Fetch_w_callback{ # Main DBI retrieval mechanism----
my ($sql, $callback) = @_;
my $state = $_[2] ||= {}; # ** This THIRD param is CALL-by-ref **
$debug{SQL} = $sql;
(my $sth=$dbh->prepare($sql))->execute();
$state->{ROW} = 0;
while (my $row = $sth->fetchrow_hashref()){
$debug{ROW} = $state->{ROW}++;
last if $callback->($row,$state) < 0; # Return negative to quit
}
$sth->finish;
}
## Sample call, later in the code ....
Fetch_w_callback( "select client_name from xxx where cid='some-cid'",
sub{ $row->{whatever} = $_[0]->{client_name}; # SET
#Process other values );
Most people believe that if it ain't broke, don't fix it.
Engineers believe that if it ain't broke, it doesn't have enough features yet.
-
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.
|