Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number
 
PerlMonks  

Re: RFC: Placeholder creation for SQL statements

by sundialsvc4 (Abbot)
on Mar 14, 2018 at 00:52 UTC ( #1210857=note: print w/replies, xml ) Need Help??


in reply to RFC: Placeholder creation for SQL statements

Hark!   Did somebody mention my name?   (Let the Downvotes begin afresh!)

Nonetheless, I do happen to agree – if you don’t know in advance what SQL statement you are executing, and therefore how many placeholders it contains, then that’s another problem entirely.   Whereas, if you do, there is no problem remaining to be solved.

– – –

Gentlebeings™, I have in all these years never apologized for the fact that my point-of-view on such things is affected by the somewhat-curious path that my by-now long career has taken:   an admixture of Firefighter and ER Triage Nurse.   I’ve seen more than my share of cleverness, and have frankly come to loathe it, because what i-n-e-v-i-t-a-b-l-y happens is that “one day there is an exception to the rule, and then all Hell breaks loose.”   Because now we have what IBM calls a “Highly Pervasive (HIPER) change.”   And furthermore, a needless one.

The Original Programmer™ – if (s)he is still alive – is by now comfortably two or three jobs hence.   We are now the ones who are tasked with un-doing this “act of cleverness.”   (Which, I assure you, none of us anticipated when laying out the application-rehabilitation project plan.   This is the sort of thing that can result in financial loss in our chosen way of doing business.)

Therefore, I would say this:   “If you legitimately need to do this sort of thing ... if you deem that you absolutely have no alternative but to do this ... then please proceed, and please leave-behind copious documentation.”   Otherwise, pretty-please don’t do it.   Please don’t create a “HIPER hot-spot” for your successors – such as my teams – to work out, when there were no technical mandates to justify your choices.   Cut-and-paste is your friend.

To clarify:   the #1 concern that I have – as a businessman as well as a multi-language programmer – is what I call “technical spill.”   This is where the actions of a particular piece of code – or, coding practice – “spill” beyond the minimum technically-necessary boundaries, and(!) do so in such a way as to make it difficult (or, merely uncertain) to ascertain just how broadly they have “spilled.”   The Original Programmer (OP) did something to coalesce all of the use-cases that (s)he was then aware of, without fully considering that one day there would be some other case that legitimately broke the mold.   Therefore, I am now faced with the realization that the mold has been broken, and that I might now have been pushed into triage-mode as I race first to identify and then to contain the arterial bleeding “spill.”

Therefore, if I may say – and with utmost respect to the OP(!) – “this at-least smacks of exactly the sort of thing that I am talking about.”   Without(!) in any way calling into question your technical judgment as an esteemed colleague, please do think-in-advance about me.

"AtDhVaAnNkCsE" == Thanks in Advance.

  • Comment on Re: RFC: Placeholder creation for SQL statements

Replies are listed 'Best First'.
Re^2: RFC: Placeholder creation for SQL statements
by karlgoethebier (Monsignor) on Mar 14, 2018 at 08:12 UTC

    Yes. Throughout a universal cries multi-language programmer. Multi-language programmer hammers a music. The cramp chews the simplified alphabet. Multi-language programmer leaps throughout the stone inertia. Each roundabout squad speaks outside a review bible.

    Did somebody mention my name™ abbreviates the percent. An ancient retracts! The infrequent resemblance scatters the president. Without the rubbish hesitates businessman. The bookstore stimulates the given mechanic. Businessman chooses under asshole. Asshole swings near the worth. Businessman mocks asshole over a killer.

    In this sense, Karl

    «The Crux of the Biscuit is the Apostrophe»

    perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'Help

Re^2: RFC: Placeholder creation for SQL statements
by Your Mother (Bishop) on Mar 14, 2018 at 01:28 UTC

    Holy space bound cats… So very much WAT and Y. It’s probably something that should be archived, really. The moment the ship dips below the horizon and furiously green flashes forever. An expert forum on Fosbury's selachimorpha. Kekulė’s lucid dreams of an Elean f() to the subatomic.

      the real issues: why is this user not banned? Why didn't you flag this post for reaping/removal?
        • free speech board politics
        • he could continue as AM (like you do)
        • being stupid is not a crime
        AMs should have no say in board politics (cause "trolling"), so I won't elaborate more!

        Cheers Rolf
        (addicted to the Perl Programming Language and ☆☆☆☆ :)
        Wikisyntax for the Monastery

        A reply falls below the community's threshold of quality. You may see it by logging in.
Re^2: RFC: Placeholder creation for SQL statements
by LanX (Archbishop) on Mar 14, 2018 at 12:50 UTC

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1210857]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others chanting in the Monastery: (3)
As of 2019-07-17 12:38 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?