I don't see any debugging prints in there - those can really help you see what's going on. In each subroutine, just after you 'shift' the parameter(s) off of @_, print each one out just to make sure the subroutine is receiving what you think it's receiving, like:
sub get_columns ($) { my $log = shift; ### Add this ### print "get_columns sub TOP: \$log = $log\n"; my @Cols = ();
And, you should also print the sql out before each 'prepare', like:
my $sql = "SELECT * FROM $log"; ### Add this print ### print "get_columns sub just before prepare: \$sql = $sql\n"; $sth = $dbobject->prepare($sql);
You get the idea - just make sure you're getting everything you think you are. Post back your results.

In reply to Re: DBI Long File names? by hmerrill
in thread DBI Long File names? by talwyn

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.