My approach is that I hate all query builders, as I always end up fighting them to get the SQL I want.

I prefer to write and test my SQL separately from Perl and having an ORM or query builder between me and the database is one more ugly layer to debug.

My use case might not be your use case though, because I usually have several (left) joins and like to use SQL window functions or subselects to select interesting rows from the database. All query builders I've seen don't handle subselects or window functions well, and they all make it impossible to get at the SQL before running the program.

My advice would be to get more familiar with SQL as it is quite a versatile tool, but if you don't use SQL that often, I understand that a Perl wrapper is more alluring.

In reply to Re: What Do Monks Think of SQL Query Builders? by Corion
in thread What Do Monks Think of SQL Query Builders? by nysus

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.