Please let me answer in chunks, without answering all questions at once, even the imaginated once. :P

> In which case you will get two different results.

I get your point, code can't compensate bad programing.

I'd say I'll offer two alternative versions of prepare (dynamic references vs static values) and emphasize on a do which does the execution after a prepare_cached right away.

>  Maybe calling xprepare twice without calling xexecute should be forbidden (die),

Nah, but I can throw a warning if two dynamic prepares bind the same refs.

>  but they can also do that across sessions, if the optimizer sees the exact same request prepared again,

Does it mean that prepare_cached from DBI is not necessary anymore?

In any case I think that "deinterpolated" templates with placeholders are easier to cache than queries with hardcoded $names.

Again, my emphasis ATM is on the "deinterpolater" and not the SQL api.

I could think of many use cases, like generating / refactoring to printf or various HTML templates.

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

In reply to Re^6: RFC: Placeholder creation for SQL statements by LanX
in thread RFC: Placeholder creation for SQL statements 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.