Thanks for the annotation. You are surely right - and I know about the caveats of ORMs.

Of course one does not need to do it the OO way - but we really need a place to store all the stuff which has to be done whenever records are processed in any way. This can be done in an static module or in an object as well.

I think it is attractive to do both (abstraction and collecting all the code) in one step.

In regard to stored procedures I do not dare to use them, because we hat massive trouble in using triggers in our replication due to mysql-bugs (which were really tricky to hunt down) and I have no interest in bugtracing mysql's stored procedures with replication...

In reply to Re^2: Search for ORM with Multi-Table-Object Support by Xel
in thread Search for ORM with Multi-Table-Object Support by Xel

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.