Just a quick update.

Based on my research, including a post by the chap responsible for some of these packages, it would appear that Class::DBI and DBIx::Class are obsolete, and that if one is to use a Perl ORM , one should use Rose::DBI::*. That said, if the objective is primarily speed, the benchmarking page I found for Rose::DB::* would suggest that though it is much faster than any other ORM tested, one is still better off using DBI itself.

I do not know if the benchmark tests used are inadequate to show the benefits of using an ORM, or if ORM systems are just a convenience for developers that may or may not justify the poorer performance (the cost of development is, after all, a major consideration alongside the speed of an application, when deciding what to do to support the functional requirements defined for the application). I will thus study Rose::DB::*, and reserve judgement as to whether or not it's use is warranted at least in some circumstances. (Maybe someone with experience with it, or a similar ORM, would like to contribute some insight based on observations when using it in real world applications?)

Cheers

Ted

In reply to Re^3: puzzling problem with access to DB when using mod_perl by ted.byers
in thread puzzling problem with access to DB when using mod_perl by ted.byers

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.