Re: Strange HASH(0x2ced735) values

[Superior Shelving]

> On Feb 21, 2017, at 8:34 AM, Uri Guttman  wrote:
> 
> you can't trace it from the value. but you can write code where that value is 
> stuffed into the db and look for a reference vs 1 or a blank. then you can 
> dump the call stack (with caller()) or do other debugging. something is 
> putting a hash reference in there that shouldn't be doing it.

Thanks Uri, but that’s the problem - so far I haven’t been able to tell 
where it’s being generated.  That’s why I was hoping to decode that value.  
Looks like I’ll have to continue searching. :\

Frank
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

Logging SQL Queries

[SSC_perl]

I’m using DBI::Log to capture SQL queries but the log file gets huge 
exponentially.  Is there a way to filter what gets logged?  If I could 
eliminate the SELECT queries, that would help a lot.

I’ve also install Log4perl and DBIx::Log4perl.  This appears to be a 
very powerful solution, but again, I’m not seeing how to filter what gets 
logged.  I’ve read this page:

https://metacpan.org/pod/release/MJEVANS/DBIx-Log4perl-0.26/lib/DBIx/Log4perl.pm

but it’s pretty terse so maybe I’m just not seeing it.  Adding 
{dbix_l4p_logmask => DBIX_L4P_LOG_SQL|DBIX_L4P_LOG_DELAYBINDPARAM} helps some, 
but I still need more filtering.

What can I use to capture only certain SQL statements?

Thanks,
Frank
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/