After some strugglin, and some help from you wonderful monks, I managed to create a hash within a hash. I would now like to store it....

When I try to save the hash into a param however, I get the following error:

"param(): something smells fishy here. RTFM! at c:/apache/Perl/site/lib/CGI/Session.pm line 381" etc.

is it not possible to store a hash value into CGI::Session param?
ie.
$session->param("access", %access);

When I tired to find a solution to this around the net, the only thing I came across was breaking up the hash into an array, saving it into the param, then when calling it re-storing it into a hash before using it. This sounds like it should be unecessary, and potentially resource-consuming if almost every page I use will require it...

Any suggestions are greatly appreciated!
Thx again, for all your help guys!


Stenyj

In reply to Storing a Hash inside a CGI::Session Param? by Stenyj

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.