Consider separating the data extraction from the formatting so you can prove each part individually. Also, maybe sprintf is all you need.
my $result = get_query_results($dbh,$sql);
print format_query_results($result);
sub get_query_results {
my ($dbh,$sql_query) = @_;
my $sth = $dbh->prepare( $sql_query );
$sth->execute();
my $ar = $sth->fetchall_arrayref;
return $ar;
}
sub format_query_results {
my $ar = shift;
my $fmt = "%-15s %20s %15s %15s %15s %15s %15s\n";
my $heading = sprintf $fmt, qw(SQL_ID min_last_load_time
buffer_gets disk_reads executions sorts parse_calls );
my $report;
for my $rec ( @$ar ){
$report .= $heading;
$report .= sprintf $fmt, @$rec[0..6];
my $sql = SQL::Beautify->new( query => $rec->[7] );
$report .= "\n".$sql->beautify."\n";
}
return $report;
}
poj
-
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.
|