I'm curious as to how people actually implement these systems in the real world.

If you're really serious about building middle-tier OO systems on top of an RDBMS, I recommend reading the manuscript for Martin Fowler's next book, Patterns of Enterprise Application Architecture. (The manuscript will be on-line until the book is published later this year.)

The examples in the book are in Java or C#, but translate fairly well to Perl.

The short version is there are choice you need to make about locking models. These choices affect how you manage caches, and how you ensure that the right changes get written back to the database in the right order. Getting a middle-tier system working well requires a lot of careful bookkeeping.

In reply to Re: OO Perl & RDBMS Strategy Question by dws
in thread OO Perl & RDBMS Strategy Question by DamnDirtyApe

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.