Opportunity is missed by most people because it is dressed in overalls and looks like work.
-- attributed to Thomas A. Edison

I'd definitely recommend to sit down and have a look at SQL. For three reasons:

1) Abstractions have a tendency to be leaky. There's a good chance that at some point you're forced to look at the pre-built SQL anyway because something really odd is happening.

2) Proper written SQL can save your application and your database a lot of time. Putting the data selection and aggregation logic logic into the SQL can drastically reduce the amount of memory, disk I/O and network bandwidth required.

3) SQL is extremely good at hiding parallel execution. Something that might be difficult to express in Perl can be extremely simple (and also efficient) in SQL. Put differently: "If all you have is a hammer, every problem looks like a nail." (Coming from the other direction: I've seen database admins performing arithmetic calculations and string manipulation in SQL - it worked but it definitely was not pretty.)

Maybe you still decide to stick with an SQL builder because that's really all what's needed. That's alright. But SQL is pretty fantastic and well worth a look.

In reply to Re: What Do Monks Think of SQL Query Builders? by Monk::Thomas
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.