Re: $DBI::neat_maxlen and execute() and debugging

2009-05-08 Thread Bill Moseley
On Fri, May 08, 2009 at 09:48:42AM +0100, Tim Bunce wrote: > > The callbacks can not only see the params, they can change them. > There are examples in the 70callbacks.t file. I suspect I'm missing something obvious. Do you mean the section? my $attr; eval { $dbh->quote_identifier('foo'

Re: $DBI::neat_maxlen and execute() and debugging

2009-05-08 Thread Tim Bunce
On Thu, May 07, 2009 at 10:03:41PM -0700, Bill Moseley wrote: > Hi Tim, > > On Fri, May 08, 2009 at 12:59:03AM +0100, Tim Bunce wrote: > > > > It might be more efficient/effective to use callbacks to enable tracing > > in just the calls you're interested in. Callbacks are (still) > > undocumented

Re: $DBI::neat_maxlen and execute() and debugging

2009-05-07 Thread Bill Moseley
Hi Tim, On Fri, May 08, 2009 at 12:59:03AM +0100, Tim Bunce wrote: > > It might be more efficient/effective to use callbacks to enable tracing > in just the calls you're interested in. Callbacks are (still) > undocumented, but the test file is pretty clear: > http://cpansearch.perl.org/src/TIMB/D

Re: $DBI::neat_maxlen and execute() and debugging

2009-05-07 Thread Tim Bunce
On Thu, May 07, 2009 at 10:08:52AM -0700, Bill Moseley wrote: > I can set $DBI::neat_maxlen to have DBI trace output show the complete > statements, but execute still is truncated. > > execute(1, 2, ...)= '0E0' at dbi_neat.pl line 91 > > Is there an equivalent "neat" setting to show all the

$DBI::neat_maxlen and execute() and debugging

2009-05-07 Thread Bill Moseley
I can set $DBI::neat_maxlen to have DBI trace output show the complete statements, but execute still is truncated. execute(1, 2, ...)= '0E0' at dbi_neat.pl line 91 Is there an equivalent "neat" setting to show all the bind variables? Also, I want to hook into the trace to be able to select