Thanks!

I experimented, and the following

{
   local $sth->{TraceLevel} = "2|SQL";
   $rv = $sth->execute(@args)
     or die $sth->errstr;
}

[download]

Produced the desired output, unfortunately surrounded by some verbose lines (see second paragraph). Reducing the trace level eliminated the information.

    DBI::st=HASH(0x2910b18) trace level set to 0x100/2 (DBI @ 0x0/0) i
+n DBI 1.623-ithread (pid 7420)
    -> execute for DBD::mysql::st (DBI::st=HASH(0x2910ab8)~0x2910b18 '
+xLangsdorf') thr#309f18
   Called: dbd_bind_ph
 -> dbd_st_execute for 02497600
    >- dbd_st_free_result_sets
    <- dbd_st_free_result_sets RC -1
    <- dbd_st_free_result_sets
mysql_st_internal_execute MYSQL_VERSION_ID 50147
>parse_params statement SELECT *
   FROM ksr_bf_utf8.t_user_portal
   WHERE f_client = ?

Binding parameters: SELECT *
   FROM ksr_bf_utf8.t_user_portal
   WHERE f_client = 'xLangsdorf'

 <- dbd_st_execute returning imp_sth->row_num 19
    <- execute= ( 19 ) [1 items] at placeholder.pl line 57
    -> STORE for DBD::mysql::st (DBI::st=HASH(0x2910b18)~INNER 'TraceL
+evel' 0) thr#309f18
        -> dbd_st_STORE_attrib for 02497600, key TraceLevel
        <- dbd_st_STORE_attrib for 02497600, result 0
    <- STORE= ( 1 ) [1 items] at placeholder.pl line 56

[download]

So I'd need to redirect the trace to a variable and parse the output for a paragraph starting with 'Binding parameters: ' in case of error...

something like 

   open my $trace_fh, ">", \ my $trace_out;
   
{
   $sth->trace("2|SQL", $trace_fh );
   $rv = $sth->execute(@args)
     or die parse($trace_out) . "\n" .$sth->errstr;
}

[download]

Thanks again! :)

Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!

In reply to Re^2: DBI.pm: composing and debugging MySql placeholders by LanX
in thread DBI.pm: composing and debugging MySql placeholders 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.