Re: looking for a patch or workaround for err / errstr bug
On 27/06/13 21:17, Robert Dodier wrote: Hi, I think I have run into this bug; https://rt.cpan.org/Public/Bug/Display.html?id=71555 I am working on a 64-bit Windows Server 2008 system and 32-bit Strawberry Perl (32-bit since it appears that there is a module I need which doesn't work with 64-bit). perl/vendor/lib/DBD/mysql.pm says $VERSION = '4.022' in it. Does anyone know of a patch or workaround for bug #71555? Thanks for any advice. best, Robert Dodier I think you might find this is now fixed in DBD-mysql-4.024. Martin
looking for a patch or workaround for err / errstr bug
Hi, I think I have run into this bug; https://rt.cpan.org/Public/Bug/Display.html?id=71555 I am working on a 64-bit Windows Server 2008 system and 32-bit Strawberry Perl (32-bit since it appears that there is a module I need which doesn't work with 64-bit). perl/vendor/lib/DBD/mysql.pm says $VERSION = '4.022' in it. Does anyone know of a patch or workaround for bug #71555? Thanks for any advice. best, Robert Dodier
State of DBD::mysql maintenance (was: looking for a patch or workaround for err/errstr bug)
On Thu, Jun 27, 2013 at 01:17:32PM -0700, Robert Dodier wrote: Hi, I think I have run into this bug; https://rt.cpan.org/Public/Bug/Display.html?id=71555 I am working on a 64-bit Windows Server 2008 system and 32-bit Strawberry Perl (32-bit since it appears that there is a module I need which doesn't work with 64-bit). perl/vendor/lib/DBD/mysql.pm says $VERSION = '4.022' in it. Does anyone know of a patch or workaround for bug #71555? I was amazed and dissapointed that such a serious apparent bug has gone without even a comment for over 18 months. Then I looked at the RT queue for DBD::mysql https://rt.cpan.org/Public/Dist/Display.html?Name=DBD-mysql and felt sad at the apparent neglect. 127 bugs (7 critical) of which over half are still 'New'. On the other hand, I see the code is on github (along with 13 other bug reports) at https://github.com/CaptTofu/DBD-mysql and Patrick seems active in recent months. I'd like to know why there hasn't been more activity on this and the other critical bugs. Do the DBD::mysql maintainers need more help? If you're a DBD::mysql user and care about the future of the code, please help out. Tim.
