You are filling up the hash just fine, but the problem is that you're going about retrieving the data from it all wrong. The hash %db_processes is a different variable than @db_processes the array. In your foreach statement, you are trying to get data out of the array variable (psst, using strict would have pointed this out) which is why you aren't getting anything at all to print.

To get back data from a hash in a similar way, either use keys, each, or values. If it were me, I'd use each in this case:

while (my($key, $hashy) = each %db_process) { # same inner loop # also, since $hashy is anticipated to be a HASH reference, # you can't do $hashy->[0], etc. # you must use $hashy->{key} (with the curly, not square brackets) }

PS: Yay, my 100th post.

blokhead


In reply to Re: Hash usage by blokhead
in thread Hash usage by jblapham

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.