I would ask that you rethink using PM as a form of "parallel processing". If there are obvious resources that you know about which you have not yet checked, it saves time for all of us for you to check them first. Based on experience you will run across just as many unexpected nuggets, it will save you time, and we will have time and energy to devote to questions that help people more directly..

Note that even while deploring the tone of a response to you I reinforced the basic point that documentation is to be checked first. The answers that come here are a volunteer resource. Furthermore the people giving them are often experienced and qualified professionals. Our time and energy is likely worth at least what yours is if we were not choosing to volunteer it, so please treat it that way. (And our not entirely secret plot is to infect you with the attitudes, values, and knowledge that make us able to volunteer so that you turn around and eventually do likewise. Now please look into this white light and forget all about this...)

For more on the cultural underpinnings that lead to our acting this way, I highly recommend Re: Newby Query Comment by davorg.

In reply to Re (tilly) 3: Getting MySQL Data into an Array. by tilly
in thread Getting MySQL Data into an Array. by cdherold

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.