Re: DBD::mysql Bugs

Jeff Bisbee wrote:
> I ran into a problem yesterday where 'mysql_use_result' and
> 'mysql_server_prepare' don't play nicely together.  There is bug
> reported to bugs.mysql.com here

Interesting, I would have expected that to be a common use case. Hmm, I
wonder if the fix for RT bug #49719 caused the problem you are seeing.

> That got me wondering if that bug was also in CPAN RT.  I was then
> amazed to see that there are currently 55 open issues, with some being
> over 4 years old!
> 
> I'm just wondering a couple things as a result:
> 
> *  Who is ultimately responsible for DBD::mysql (is someone paid at
> mysql to maintain it or is it CAPTTOFU, FRAMM, JIMW, RANGER, RUDY, and
> WILSON from cpan rt?)

These days, I believe that would be CAPTTOFU.  I maintained DBD::mysql
through 2.9x where Patrick Galbraith(CAPTTOFU) took over.  At that time
he was being paid by  mysql to maintain it (and I was low on cycles),
although, I don't know if he is still working on the driver for the
mysql people or not.  I believe that the others that you listed are
people to whom Patrick has given commit access.

> *  Is anyone comparing cpan's rt to bugs.mysql.com and actually fixing them?
> *  An finally the real question I'm interested in, what is an ETA

From watching the mailing lists, Patrick has been rather responsive to
new bugs and fixes them as they come to his attention.  I assume that he
is aware the issue now, if he was not before.  In the mean time,
however, you might want to look at trying an older version (pre 4.013)
to see if that works.  If you have an immediate need for a fix and
Patrick is too busy, I'd be happy to look at the issue, and take a crack
at writing up a patch.


HTH,

-r

-- 
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe:    http://lists.mysql.com/[email protected]