On 18/04/2013 20:09, Paul DuBois wrote:
On Apr 18, 2013, at 12:07 PM, Patrick Galbraith wrote:

Lyle,

To be certain, they don't wish to "kill" DBD::mysql. They are really trying to 
define what Oracle supports and what they do not. The were very helpful in painstakingly 
migrating the bugs from their system manually to RT. Albeit, I have my work cut out for 
me now :)
I'm not an official spokesman for Oracle, although I do work for them.

I am unaware of any effort against DBD::mysql. Nor has Oracle made any effort 
to dissuade me from writing about DBD::mysql, e.g., at 
http://www.kitebird.com/mysql-book/. (You can view that URL as a shameless plug 
or just evidence in support of the preceding claims, your choice. :-))

Paul, that's good to hear :)

Patrick, I've since noticed more issues that I covered in my patch. Hopefully next month I'll get chance to give it a more thorough check.


Lyle


Regards,

Patrick

On Apr 11, 2013, at 8:28 PM, Lyle <webmas...@cosmicperl.com> wrote:

On 12/04/2013 00:58, Darren Duncan wrote:
On 2013.04.11 4:37 PM, Lyle wrote:
Hmm... Got a reply to my bug report and it's a bit worrying:
http://bugs.mysql.com/bug.php?id=68266

Seems like MySQL don't want to directly support DBD::mysql any more. Whether you
like mysql or not, that's a heavily used DBD.
I'm not aware that DBD::mysql was ever supported through the general MySQL bug 
reporter, and I understood it was a separate project.
It most certainly was, for example:
http://bugs.mysql.com/bug.php?id=20153

The DBD::mysql docs still tell you to report bugs there. Even I was able to 
submit a bug to their DBD::mysql category just last February, they've only just 
removed it from the bug reporter.

I think Patrick Galbraith is the person you should ask about this matter, as 
Patrick has been the one releasing DBD::mysql on CPAN for many years, a full 
decade at this point.
I've just joined the p...@lists.mysql.com mailing list. It'll be interesting to 
see if that list stays or gets removed as well.


Lyle

-- Darren Duncan




Reply via email to