The SQL can stay like it is, and the session variables you have will map directly into Perl scalars. As you noted, you can either incorporate them directly into the SQL, or make separate calls like you are now to populate them, then bind or interpolate them into the main SQL (although I don't see where you're using start_date and end_date).
The break and compute you'll have to do by yourself. There are different ways, but a simple outline may be:
And of course, spool spoolfile is just open OUT, ">spoolfile"; select OUT; or something like that.my $lastcountry = ''; my $totaldowntime = 0; while (my $row = $sth->fetch()) { (..., $country, $downtime, ...) = @$row; $totaldowntime += $downtime; if ($country ne $lastcountry) { # note this will be true first time thru the loop print $totaldowntime; $totaldowntime = 0; next_page(); # however you accomplish this in your setting }
What's going to take work is "set markup html". I've never used it, but I presume it's got some sort of automated layout, like a table or something. You'll have to cook up the layout yourself, but the good news is that you have full control over the output, and you can use tools like HTML::Template or Template::Toolkit to make the job easier. (I'd recommend the former if you've never used HTML templates before -- it's easier to get started.)
HTH
In reply to Re(3): Sqlplus -> DBD::Oracle Question
by VSarkiss
in thread Sqlplus -> DBD::Oracle Question
by set_uk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |