A particularly cool variation on this theme, is when you have different 'levels' of data, with increasing cost of retrieval from your datastore.

For example, assume you have a database of people, with very basic data bout them stored in a "People" table, one row per person, keyed on SSN. Other less frequently data is stored in a variety of other tables (ie: all of their grades from every class they ever took is stored in some table keyed by SSN & year; their current & historic clothing sizes are another table keyed by SSN, year & clothing-type; etc..). And still more data about the person is very aggregate in nature, and requires 'expensive' computation (ie: their grade to waste size ratio for each year)

If you typically only care about the "core" data on a person, and occasionally care about their clothing sizes, and very infrequently care about *ALL* of the data you have on them, then you can divide up the data by how easy/fast it can be retrieved, and change your %allowed_attrs hash into an %attr_populator hash, that stores a method ref you can call to retrive data at that level -- if it hasn't allready been retrived. so in the common case, you are only calling the very fast _get_core_data() method, but when neccessary you call the more obscure _get_clothing_sizes() method.

Something along the lines of... 

%attr_populator = {
     name => \_get_core_data,
     bday => \_get_core_data,
     sizes => \_get_clothing_sizes_data,
     grades => \_get_grade_data,
     complex => \_get_really_expensive_data,
};

sub AUTOLOAD {
  my $self=shift;
  my $attr=$AUTOLOAD;
  unless (exists $attr_populator{$attr}) die "Hey, that attribute does
+ not exist!\n";
  &{$att_populator{$attr}}($self) unless (exists $self->{$attr})
  return $self->{$attr};
}

[download]

In reply to Re: Re: Point of AUTOLOAD in a database environment? by hossman
in thread Point of AUTOLOAD in a database environment? by janjan

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.