Hello SpaceCowboy,
the first tool to code reuse are subroutines; see perlsub then if you can generalize a behaviour you can create your own module.
As Corion++ already suggested you can have all sql statements in the main program and I'd use sub also for each steps: this help a lot having the main flow of the program short and clean.
use strict;
use warnings;
use DBI;
use Term::ReadKey; # use mode 2 'noecho' to ask for the connection pwd
+, then revert to normal
my $dbh = init_DB_connection;
my $first_step_result = do_first_step;
# https://metacpan.org/pod/DBI#do returns NRows, undef or -1
if ( !defined $first_step_result ){ ... } # report errors and exit
elsif ( -1 == $first_step_result ){ ... } # perhaps this is a succe
+ss in case of create table, dunno, execute second_step
elsif ( $first_step_result > 0 ){ ... } # $first_step_result rows
+ affected
else { ... } # got unexpected $first_s
+tep_result
sub init_DB_connection { ... } # return $dbh on success, exit if error
+s
sub do_first_step { ... }
...
L*
There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
-
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.
|