Hi,
I've a several 100 thousand line application. I did not introduce this issue,
but I need to fix it.
prepare_cached(SELECT foo FROM A where X = ?)
statement handle MyDBI::st=HASH(0xd630194) was still active at X.pm
I've tried turning on $dbh->(12, 'file.trace') and looking for all things that
shared the statement handles
address. Then seeing if there was a FETCH= undef -- the end of a while loop, or
finsih= 1 -- $sth->finish() was called.
That took a long time and everything seemed okay. Then I pains-takenly figured out all the 'prepare_cached' involved in
the code path. I then add $sth->finish() for kicks everywhere even when I knew I "didn't need it" per the DBI docs
about it. This didn't help.
Is there any way (preferably easy) to track this down ?
Its going to have to programatic as the amount of code involved is not manageable and I'm unable to reduce it. If I
could reduce it I could fix it :)
--
------------------------------------------------------------------------
Philip M. Gollucci ([EMAIL PROTECTED]) 323.219.4708
Consultant / http://p6m7g8.net/Resume/resume.shtml
Senior Software Engineer - TicketMaster - http://ticketmaster.com
1024D/A79997FA F357 0FDD 2301 6296 690F 6A47 D55A 7172 A799 97F
"In all that I've done wrong I know I must have done something right to
deserve a hug every morning and butterfly kisses at night."
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ /
/ /|_/ / // /\ \/ /_/ / /__
/_/ /_/\_, /___/\___\_\___/
<___/
