The problem is that the underlying gdbm library stores mere strings as the value of an entry, not Perl data structures. And the Perl module GDBM_File (which is just a thin wrapper around the library) doesn't provide any automatic serialization/deserialization either.

In other words, you'd have to do that yourself (using Storable, Data::Dumper, whatever) if you want to stick with GDBM.  I.e., convert the Perl data structure into a sequence of bytes (serialization) upon writing, which you'd then have to convert back into a Perl data structure (deserialization) after having read the string from the DB.  Personally, I would rather use another module better suited for the task (like the already mentioned DBM::Deep).

In reply to Re^5: Problem: read a GDBM hash with 2 keys in perl by almut
in thread Problem: read a GDBM hash with 2 keys in perl by cscat

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.