Opinion wrap-up:

LanX: poses the question.  It sounds like he seeks to get  DBIC to be exempt from the bad reputation that ORM's have for some/many (?) people (never mind whether the bad rep is deserved or not) by way of un-ORMing it into something else.

LanX's colleague:  DBIC is ORM (sounds like bad feelings)

cavac: Sounds kinda slow (= bad feelings)

haukex: DBIC is ORM (no bad feelings)

haj: DBIC is ORM (maybe some bad feelings but blames DBA)

Arunbear: DBIC is an ORM (no bad feelings)

erix: 'who needs ORM or ORMy stuff?!' - bad feelings, but not deeply: I can imagine that it can be handy when:
  - multiple underlying DBMS (although, I severely doubt 
  - SQL/DBMS-challenged developers, or DBAs keeping devs at arms' length of the DB.
  - separating SQL from applications in large projects (in smaller projects much less useful, I'd say; maybe even bad

Looking at that (alas, n=small), it is conspicuous that there are no strong arguments in favour of ORMs nor is there any strong language against ORMs. Maybe the difference is not so important, whatever the terminology.

In reply to Re: Terminology: Is DBIx::Class an ORM? by erix
in thread Terminology: Is DBIx::Class an ORM? by LanX

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.