I am writing a project in Moose, which I'm fairly new to. The project will store and analyze a large amount of data, which for convenience purposes is being stored in a huge hash. What I would like is to, sometime in the future, tie the hash to a Moose object controlling a database so as to optimize data accesses. So, basically I know I want something like this: 
  package App::Foo;
  use Moose;
  
  has 'db' => ( isa => 'App::Foo::DB' );

[download]
where App::Foo::DB is just a blessed hash with no methods, so that I can use it in expressions like: 
  $self->db->{a}{b}{c} = 'foo';

[download]
What I don't know, is if its possible to rewrite App::Foo::DB so as to define a type of hash that is tied to a Moose class, and if so, how one should go about it. I guess the real question is how to define a Moose class with the interface of a tied hash.

In reply to Tied Hash Interface to Moose Object. by swestrup

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.