You should consider using RaiseError when you connect like ...
my $dbh = DBI->connect("dbi:SQLite:dbname=request_db","","", {RaiseErr
+or => 1});

[download]

Now you will not have to check for errors after every dbi method you call. Your code would then be something like ...
my $dbh;
eval {
   $dbh = DBI->connect("dbi:SQLite:dbname=request_db","","", {RaiseErr
+or => 1});
   $dbh->do($createTableSQL);
};
if ($@) {
   # handle error here
   # the error will be in the $@ variable
   # the error raised could be from the connect or the do methods
}

[download]

Note that I change your prepare/execute/finish to just a do.
This is more concise way of executing DDL statements.

In reply to Re: How should I handle $sth->execute() errors? by mifflin
in thread How should I handle $sth->execute() errors? by Plankton

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.