The sugested $dbh->trace (...) is of course the documented way of tracing what actually happens with your code on the way to and from the database.

You didn't tell what database you are using, but some (DBD::Oracle, DBD::Pg, and DBD::Unify that I know of) have implemented the dbd_verbose attribute, in which you can track what the DBD backend is doing with your data. Read the documentation of your DBD for how it - if at all - implements dbd_verbose. The huge advantage of dbd_verbose over $dbh->trace is that you do not get to see the DBI messages, which I already trust enough not to be part of my doubts.


Enjoy, Have FUN! H.Merijn

In reply to Re: Debugging DBI placeholders by Tux
in thread Debugging DBI placeholders by davies

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.