A recent discussion on the subject of SQL with
Zigster
and other friends has let me to this question:
With all the sub selecting, maxing, having and grouping
and other such SQLisms associated with quite complex queries,
wouldn't it just be easier to select the lot into perl (row
by row or otherwise) and do the processing there? Assuming,
that is, (or maybe not) that the program receiving the data
was perl anyway.
As there will be many factors, here are some points raised:
Would it be:
I have not benchmarked this, but my hunch says all of the above.
How would it fair if there was one or many tables involved?
Would it depend on the database?
In some cases, I imagine it would be vlaid to completely
remove the database and replace it with flat files.
Another hunch of mine say that it will simpy come down to
"it depends what you are doing". But that would be a shame.
Your thoughts would be appreciated.
--
Brother Marvell
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.