I am trying to use Text::Graph and it says it is called as follows: 
my $graph = Text::Graph->new( 'Bar' );
print $graph->to_string( [1,2,4,5,10,3,5],
                         labels => [ qw/aaaa bb ccc dddddd ee f ghi/ ]
+,
                       );

[download]
I am looking through a database result set and generating what I thought was an "array" as follows: 
while (@rowdata = $sth->fetchrow_array()) {
    push (@chart_data, $rowdata[2]+0);
    push (@chart_labels, $rowdata[0].' '.$rowdata[1].':00');
}
$graph->to_string(@chart_data, labels=>@chart_labels);

[download]

The issue is that my "array" craps out when I call 

$graph->to_string
as I do not think it is the "same kind of array" that it is expecting.

How do I create the kind of "array" the example call is expecting?

In reply to How to create a "proper" array? by bfdi533

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.