Re: selectrow_hashref() propagating wrong message (bug in DBD::mysql)

Hello All,

I have started to see random "fetch() without execute()" messages on a
production when mysql is under heavy load.  I believe the thread below
describes my problem (from dbi-dev mailing list circa 2007).  The production
system is currently using an older version of DBD::mysql and I wanted to
make sure this bug was fixed before scheduling an upgrade.  I looked through
changesets on github and couldn't pinpoint when it was fixed.  I tried to
compare the error handling between trunk and my version and couldn't see any
major difference (forgive me, it is my first time looking through dbd::mysql
source).  My question is was this fixed?  And if so, what was the fix?

Thanks,

Paul

===============

HTML version of the thread =>
http://www.nntp.perl.org/group/perl.dbi.dev/2007/03/msg4881.html

===============

From:
Patrick Galbraith
Date:
March 5, 2007 13:51
Subject:
Re: selectrow_hashref() propagating wrong message (bug in DBD::mysql)
Message ID: