You need to add more error checking. Often the man pages are very terse and skip it, but it becomes really valuable once you begin writing code of any significant length.

In this case, a quick look at the GD::Graph::Data POD suggests that calling the error() method might tell you what went wrong.

Lots of additional error info is discussed in the GD::Graph::Error POD, including the $GD::Graph::Error::Debug variable which might also give you a better hint.

And use RaiseError on your DBI handle! See the DBI docs if you aren't familiar with it. It makes your error handling both simpler and more robust since you don't have to add error checks, and you don't have to remember to add error checks.

In reply to Re: Problems with references using GD::Graph::Data by mla
in thread Problems with references using GD::Graph::Data by gary kuipers

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.