Re: State of DBD::mysql maintenance
On Tue, 27 Aug 2013 22:11:20 -0400, Patrick Galbraith p...@patg.net wrote: Hi all, I'm here. Been really busy and wanting to get out another release and will do so this week to get some movement. I have a ton of bugs in RT, some really old that Oracle kindly copied from their bug system to RT and could use help verifying those, many already being fixed, and many for versions that make no sense to fix per se . I also could use help with the UTF8 issues as well as some of the threading issues. I would love to move the code to https://github.com/perl5-dbi. Who can I talk to about making that happen? I can help if you want to. Are you on irc on a somewhat regular basis? irc.perl.org/6667 #dbi (I am Tux or [Tux]) Regards, Patrick On Jun 28, 2013, at 10:42 AM, Tim Bunce tim.bu...@pobox.com wrote: On Fri, Jun 28, 2013 at 04:37:44AM -0400, Michiel Beijen wrote: From: Martin J. Evans boh...@ntlworld.com Anyway, here is my offer to DBD maintainers and in particular DBD::mysql maintainers. If you want some help with rt queues in particular whether that be simply some house keeping on the queue itself (I'd need privilege to do that bit - cpan id MJEVANS) or bug finding/fixing I'm prepared to help out where I can - just ask. That's great. I can give you access for that Martin by making you a co-maint, but naturally I'm reluctant to do so without the approval of the current maintainers. I'd also be willing to help out fixing up some of the issues Thanks for the offer Mike. although I do not have XS-skills (such as mje) and I have limited time, We all have different skills to offer, and limited time, that's why working together as a team is so effective. I'd really like to hear from any of the current maintainers. I'd also specifically like to ask if they'd be happy to move the repo under the umbrella of the github perl5-dbi organization https://github.com/perl5-dbi where many people would be able to help directly. Tim. -- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.19 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
Re: State of DBD::mysql maintenance
On Wed, 28 Aug 2013 08:36:12 +0200, H.Merijn Brand h.m.br...@xs4all.nl wrote: On Tue, 27 Aug 2013 22:11:20 -0400, Patrick Galbraith p...@patg.net wrote: Hi all, I'm here. Been really busy and wanting to get out another release and will do so this week to get some movement. I have a ton of bugs in RT, some really old that Oracle kindly copied from their bug system to RT and could use help verifying those, many already being fixed, and many for versions that make no sense to fix per se . I also could use help with the UTF8 issues as well as some of the threading issues. I would love to move the code to https://github.com/perl5-dbi. Who can I talk to about making that happen? I can help if you want to. Are you on irc on a somewhat regular basis? irc.perl.org/6667 #dbi (I am Tux or [Tux]) The copy went well: there is now a https://github.com/perl5-dbi/DBD-mysql with no reference(s) to github.com:CaptTofu/DBD-mysql.git I did not (yet) change the refs in lib/DBD/mysql.pm and META.yml from git://github.com/CaptTofu/DBD-mysql.git the replica address What I do not know how to do is make you a committer to this repo with you also being a committer to all projects in perl5-dbi and I do not know Tim's policy/policies in this. -- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.19 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
Re: State of DBD::mysql maintenance
Tux, Thank you for your offer! I am in several channels on IRC. Most often #openstack-infra, #openstack, though also #maria, #mysql and #percona. My nick is CaptTofu. Regards, Patrick On Aug 28, 2013, at 2:36 AM, H.Merijn Brand h.m.br...@xs4all.nl wrote: On Tue, 27 Aug 2013 22:11:20 -0400, Patrick Galbraith p...@patg.net wrote: Hi all, I'm here. Been really busy and wanting to get out another release and will do so this week to get some movement. I have a ton of bugs in RT, some really old that Oracle kindly copied from their bug system to RT and could use help verifying those, many already being fixed, and many for versions that make no sense to fix per se . I also could use help with the UTF8 issues as well as some of the threading issues. I would love to move the code to https://github.com/perl5-dbi. Who can I talk to about making that happen? I can help if you want to. Are you on irc on a somewhat regular basis? irc.perl.org/6667 #dbi (I am Tux or [Tux]) Regards, Patrick On Jun 28, 2013, at 10:42 AM, Tim Bunce tim.bu...@pobox.com wrote: On Fri, Jun 28, 2013 at 04:37:44AM -0400, Michiel Beijen wrote: From: Martin J. Evans boh...@ntlworld.com Anyway, here is my offer to DBD maintainers and in particular DBD::mysql maintainers. If you want some help with rt queues in particular whether that be simply some house keeping on the queue itself (I'd need privilege to do that bit - cpan id MJEVANS) or bug finding/fixing I'm prepared to help out where I can - just ask. That's great. I can give you access for that Martin by making you a co-maint, but naturally I'm reluctant to do so without the approval of the current maintainers. I'd also be willing to help out fixing up some of the issues Thanks for the offer Mike. although I do not have XS-skills (such as mje) and I have limited time, We all have different skills to offer, and limited time, that's why working together as a team is so effective. I'd really like to hear from any of the current maintainers. I'd also specifically like to ask if they'd be happy to move the repo under the umbrella of the github perl5-dbi organization https://github.com/perl5-dbi where many people would be able to help directly. Tim. -- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.19 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
Re: State of DBD::mysql maintenance
By copy, did you check out the repo from git://github.com/CaptTofu/DBD-mysql.git , the push it up to the new repo as a different remote? On Aug 28, 2013, at 3:02 AM, H.Merijn Brand h.m.br...@xs4all.nl wrote: On Wed, 28 Aug 2013 08:36:12 +0200, H.Merijn Brand h.m.br...@xs4all.nl wrote: On Tue, 27 Aug 2013 22:11:20 -0400, Patrick Galbraith p...@patg.net wrote: Hi all, I'm here. Been really busy and wanting to get out another release and will do so this week to get some movement. I have a ton of bugs in RT, some really old that Oracle kindly copied from their bug system to RT and could use help verifying those, many already being fixed, and many for versions that make no sense to fix per se . I also could use help with the UTF8 issues as well as some of the threading issues. I would love to move the code to https://github.com/perl5-dbi. Who can I talk to about making that happen? I can help if you want to. Are you on irc on a somewhat regular basis? irc.perl.org/6667 #dbi (I am Tux or [Tux]) The copy went well: there is now a https://github.com/perl5-dbi/DBD-mysql with no reference(s) to github.com:CaptTofu/DBD-mysql.git I did not (yet) change the refs in lib/DBD/mysql.pm and META.yml from git://github.com/CaptTofu/DBD-mysql.git the replica address What I do not know how to do is make you a committer to this repo with you also being a committer to all projects in perl5-dbi and I do not know Tim's policy/policies in this. -- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.19 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
Re: State of DBD::mysql maintenance
On Wed, 28 Aug 2013 08:01:38 -0400, Patrick Galbraith p...@patg.net wrote: By copy, did you check out the repo from git://github.com/CaptTofu/DBD-mysql.git Yes, then edited .git/config to point to the new repo as master and push the push it up to the new repo as a different remote? Correct On Aug 28, 2013, at 3:02 AM, H.Merijn Brand h.m.br...@xs4all.nl wrote: On Wed, 28 Aug 2013 08:36:12 +0200, H.Merijn Brand h.m.br...@xs4all.nl wrote: On Tue, 27 Aug 2013 22:11:20 -0400, Patrick Galbraith p...@patg.net wrote: Hi all, I'm here. Been really busy and wanting to get out another release and will do so this week to get some movement. I have a ton of bugs in RT, some really old that Oracle kindly copied from their bug system to RT and could use help verifying those, many already being fixed, and many for versions that make no sense to fix per se . I also could use help with the UTF8 issues as well as some of the threading issues. I would love to move the code to https://github.com/perl5-dbi. Who can I talk to about making that happen? I can help if you want to. Are you on irc on a somewhat regular basis? irc.perl.org/6667 #dbi (I am Tux or [Tux]) The copy went well: there is now a https://github.com/perl5-dbi/DBD-mysql with no reference(s) to github.com:CaptTofu/DBD-mysql.git I did not (yet) change the refs in lib/DBD/mysql.pm and META.yml from git://github.com/CaptTofu/DBD-mysql.git the replica address What I do not know how to do is make you a committer to this repo with you also being a committer to all projects in perl5-dbi and I do not know Tim's policy/policies in this. -- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.19 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
Re: State of DBD::mysql maintenance
Hi all, I'm here. Been really busy and wanting to get out another release and will do so this week to get some movement. I have a ton of bugs in RT, some really old that Oracle kindly copied from their bug system to RT and could use help verifying those, many already being fixed, and many for versions that make no sense to fix per se . I also could use help with the UTF8 issues as well as some of the threading issues. I would love to move the code to https://github.com/perl5-dbi. Who can I talk to about making that happen? Regards, Patrick On Jun 28, 2013, at 10:42 AM, Tim Bunce tim.bu...@pobox.com wrote: On Fri, Jun 28, 2013 at 04:37:44AM -0400, Michiel Beijen wrote: From: Martin J. Evans boh...@ntlworld.com Anyway, here is my offer to DBD maintainers and in particular DBD::mysql maintainers. If you want some help with rt queues in particular whether that be simply some house keeping on the queue itself (I'd need privilege to do that bit - cpan id MJEVANS) or bug finding/fixing I'm prepared to help out where I can - just ask. That's great. I can give you access for that Martin by making you a co-maint, but naturally I'm reluctant to do so without the approval of the current maintainers. I'd also be willing to help out fixing up some of the issues Thanks for the offer Mike. although I do not have XS-skills (such as mje) and I have limited time, We all have different skills to offer, and limited time, that's why working together as a team is so effective. I'd really like to hear from any of the current maintainers. I'd also specifically like to ask if they'd be happy to move the repo under the umbrella of the github perl5-dbi organization https://github.com/perl5-dbi where many people would be able to help directly. Tim.
Re: State of DBD::mysql maintenance
On Fri, Jul 12, 2013 at 02:27:56PM +0100, Rudolf Lippan wrote: On Fri, 28 Jun 2013 15:42:36 +0100, Tim Bunce tim.bu...@pobox.com wrote: I can give you access for that Martin by making you a co-maint, but naturally I'm reluctant to do so without the approval of the current maintainers. Sorry, I have been away from email for the past couple of weeks. I have no objections, but I don't want to step on Patrick's toes. Thanks for that. I'd also be willing to help out fixing up some of the issues Thanks for the offer Mike. although I do not have XS-skills (such as mje) and I have limited time, We all have different skills to offer, and limited time, that's why working together as a team is so effective. I am willing to pitch in where needed. I'd have to get back up to speed. I can integreate patches, take care of some of the XS stuff, and spin up a release, but again, I don't want to step on Patrick's toes. Understood. Thanks Rudolf. I'd really like to hear from any of the current maintainers. I'd also specifically like to ask if they'd be happy to move the repo under the umbrella of the github perl5-dbi organization https://github.com/perl5-dbi where many people would be able to help directly. I am easy, but I'd be interested in Patrick's take on it. I appreciate that it's holiday season so I don't want to rush. Does anyone have alternative contect information for Patrick? Tim.
Re: State of DBD::mysql maintenance
On Fri, 28 Jun 2013 15:42:36 +0100, Tim Bunce tim.bu...@pobox.com wrote: On Fri, Jun 28, 2013 at 04:37:44AM -0400, Michiel Beijen wrote: From: Martin J. Evans boh...@ntlworld.com Anyway, here is my offer to DBD maintainers and in particular DBD::mysql maintainers. If you want some help with rt queues in particular whether that be simply some house keeping on the queue itself (I'd need privilege to do that bit - cpan id MJEVANS) or bug finding/fixing I'm prepared to help out where I can - just ask. That's great. I can give you access for that Martin by making you a co-maint, but naturally I'm reluctant to do so without the approval of the current maintainers. Sorry, I have been away from email for the past couple of weeks. I have no objections, but I don't want to step on Patrick's toes. I'd also be willing to help out fixing up some of the issues Thanks for the offer Mike. although I do not have XS-skills (such as mje) and I have limited time, We all have different skills to offer, and limited time, that's why working together as a team is so effective. I am willing to pitch in where needed. I'd have to get back up to speed. I can integreate patches, take care of some of the XS stuff, and spin up a release, but again, I don't want to step on Patrick's toes. I'd really like to hear from any of the current maintainers. I'd also specifically like to ask if they'd be happy to move the repo under the umbrella of the github perl5-dbi organization https://github.com/perl5-dbi where many people would be able to help directly. I am easy, but I'd be interested in Patrick's take on it. -r
Re: State of DBD::mysql maintenance
On 29/06/2013 11:09, demerphq wrote: On 28 June 2013 04:07, Paul DuBois p...@snake.net wrote: On Jun 27, 2013, at 8:56 PM, Lyle wrote: On 28/06/2013 02:34, Paul DuBois wrote: On Jun 27, 2013, at 8:16 PM, Lyle wrote: On 27/06/2013 22:22, Tim Bunce wrote: If you're a DBD::mysql user and care about the future of the code, please help out. I felt the same when I came across this during my research. I didn't have a great deal of luck in my initial efforts to reach out. It seems like Oracle/MySQL have lost a lot of interested in DBD::mysql (hence my post about this a couple of months back). Wait. That thread was about your belief that Oracle was trying to distance itself from DBD::mysql or discourage its development. Maybe I should have worded it better. The post was more to pose a question than state a belief. When I looked at the RT queue I saw the same issues that Tim has brought up now. The POD itself said to use the MySQL bug tracker and not RT, so I submitted my bug to the DBD::mysql section there. Taking into account the response I got to my patch on the MySQL bug tracker, that they removed the DBD::mysql section at the same time, the issues I found myself, the age of the last release, and the RT queue, it didn't paint a picture of this is a priority and I was given the impression that Oracle/MySQL had lost interest. I wouldn't say it's a belief, as that sounds a lot more certain. But it is the impression I get. I'm not suggesting that they want to discourage its development, just that they don't appear to view it as being as important as it once was. That would go some way to explain why it appears to have suffered from some neglect and is in need of some tlc. It's not clear to me that *Oracle* has ever had any particular view about DBD::mysql. It's not an Oracle product. It wasn't a Sun product before Oracle bought Sun. And as far as I am aware, it was not a MySQL AB product before Sun bought MySQL AB. It's true that MySQLers contributed some work to DBD::mysql, but as far as being any official company product ... I have never had that impression. Which it is not. It's simply that DBD::mysql is not an Oracle product. Oracle is not responsible to fix DBD::mysql bugs. I would assume Oracle has a vested interest in it? Why? Absent any statement from Oracle, I don't think we can say. Oracle now owns MySQL. DBD::mysql supports a lots of MySQL users... That said, if your next statement is correct, that'd be great. However, it does appear that some activity has come back. I'm not sure if anyone looked at my patch, but I have since realised that there was a lot more amiss. DBD::mysql really needs to be updated for proper MySQL *5* support. I was talking to Peter about extra hacking sessions at our last Perl meet. I'll make sure this is on the agenda. Good, thanks. I had the privilege of attending a meeting with some of the senior Oracle Mysql staff and I personally raised the subject of ongoing Oracle support for DBD::mysql. The response was most definitely not negative, they both knew the subject matter and knew that Patrick Galbraith was the maintainer. I did not get the slightly impression they have any negative approach towards the DBD::mysql. At worst their attitude was its an open source project we have no control over, but if Patrick asks for help we will do our best, which seems pretty reasonable to me. That is good news :) Possibly a sponsored hackathon or alike? Lyle
Re: State of DBD::mysql maintenance
On Fri, Jun 28, 2013 at 04:37:44AM -0400, Michiel Beijen wrote: From: Martin J. Evans boh...@ntlworld.com Anyway, here is my offer to DBD maintainers and in particular DBD::mysql maintainers. If you want some help with rt queues in particular whether that be simply some house keeping on the queue itself (I'd need privilege to do that bit - cpan id MJEVANS) or bug finding/fixing I'm prepared to help out where I can - just ask. That's great. I can give you access for that Martin by making you a co-maint, but naturally I'm reluctant to do so without the approval of the current maintainers. I'd also be willing to help out fixing up some of the issues Thanks for the offer Mike. although I do not have XS-skills (such as mje) and I have limited time, We all have different skills to offer, and limited time, that's why working together as a team is so effective. I'd really like to hear from any of the current maintainers. I'd also specifically like to ask if they'd be happy to move the repo under the umbrella of the github perl5-dbi organization https://github.com/perl5-dbi where many people would be able to help directly. Tim.
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.
Re: State of DBD::mysql maintenance
On 27/06/2013 22:22, Tim Bunce wrote: 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'. and of those I see: o a load of supplied patches and many have been applied by MICHIELB to github o quite a number of duplicates o a few that look like they may be misunderstandings or errors on the part of the reporter o 4 items marked as wishlist/enhancements - there are obviously more not marked as such o some which seem to be fixed but not marked as such e.g. rt60085 o 70+ rts over 2 year old Of the criticals some look like they might be fixed but the reporter has gone away e.g., the 6 year old 19091. The 2 year old critical 68374 looks to contain a fix by the reporter. 68169 is marked CHORNY [...] cpan.org - Fixed in 4.020 added. 72501 is --testuser switch to Makefile.PL does not work on windows (not what I'd classify as critical). 76835 contains a pull request with fix. So by my reckoning that only leaves 2 critical issues that need investigating and the others are fixed or not critical. It looks to me like a little house keeping and a new release would seriously dent the queue. As for the really old reports that situation existed with DBD::Orace a few years ago. John, Yanick and I had a concerted effort to clear up the old ones but in some cases they could not be reproduced and the reporter a) was not contactable b) wasn't using DBD::Oracle any more. In these cases I didn't see any point in keeping them open and a small few were written off. However, it was amazing what a concerted effort managed in a few weeks. 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. I've no idea if the DBD::mysql maintainers need more help. When I was actively using DBD::mysql (a lot of years ago) I supplied patches to Patrick and they were applied. Not everyone is capable of supplying patches. I'm guessing DBD::mysql is probably the most used DBD and as mysql is so easily installed by most package managers I guessed a lot more inexperienced users are using DBD::mysql and that might be leading to a load of wrong rts but the last one rejected was 3 years ago. Three years ago (I think it was just after a LPW), I suggested having a DBD team where DBD maintainers (and anyone else who was capable) could pitch in to help keep the rt queues down - there wasn't much interest. I think I repeated it again about 1 year ago with a similar result (although that may have only been on irc). Now most DBDs are in git it should be a lot easier. I also see around 25 people on #dbi regularly these days whereas 2 years ago it was probably around 5, if that. I get a feeling there is a lot of potential there if it can be stirred up a bit. I wish I could have attended the last QA hackathon as I would have been happy to work on rt queues for any of the DBDs I thought I could have helped with. I wonder if we could organise a DBI/DBD hackathon even if it was one done remotely. Anyway, here is my offer to DBD maintainers and in particular DBD::mysql maintainers. If you want some help with rt queues in particular whether that be simply some house keeping on the queue itself (I'd need privilege to do that bit - cpan id MJEVANS) or bug finding/fixing I'm prepared to help out where I can - just ask. For reasons I'm not going to go into here I will have more spare time over the next month and the DBD::ODBC queue is almost non existent and DBD::Oracle queue is almost under control so get it while you can. Martin -- Martin J. Evans Wetherby, UK
Re: State of DBD::mysql maintenance
On 27/06/2013 22:22, Tim Bunce wrote: If you're a DBD::mysql user and care about the future of the code, please help out. I felt the same when I came across this during my research. I didn't have a great deal of luck in my initial efforts to reach out. It seems like Oracle/MySQL have lost a lot of interested in DBD::mysql (hence my post about this a couple of months back). However, it does appear that some activity has come back. I'm not sure if anyone looked at my patch, but I have since realised that there was a lot more amiss. DBD::mysql really needs to be updated for proper MySQL *5* support. I was talking to Peter about extra hacking sessions at our last Perl meet. I'll make sure this is on the agenda. Lyle
Re: State of DBD::mysql maintenance
On Jun 27, 2013, at 8:16 PM, Lyle wrote: On 27/06/2013 22:22, Tim Bunce wrote: If you're a DBD::mysql user and care about the future of the code, please help out. I felt the same when I came across this during my research. I didn't have a great deal of luck in my initial efforts to reach out. It seems like Oracle/MySQL have lost a lot of interested in DBD::mysql (hence my post about this a couple of months back). Wait. That thread was about your belief that Oracle was trying to distance itself from DBD::mysql or discourage its development. Which it is not. It's simply that DBD::mysql is not an Oracle product. Oracle is not responsible to fix DBD::mysql bugs. That said, if your next statement is correct, that'd be great. However, it does appear that some activity has come back. I'm not sure if anyone looked at my patch, but I have since realised that there was a lot more amiss. DBD::mysql really needs to be updated for proper MySQL *5* support. I was talking to Peter about extra hacking sessions at our last Perl meet. I'll make sure this is on the agenda. Good, thanks. Lyle
Re: State of DBD::mysql maintenance
On 28/06/2013 02:34, Paul DuBois wrote: On Jun 27, 2013, at 8:16 PM, Lyle wrote: On 27/06/2013 22:22, Tim Bunce wrote: If you're a DBD::mysql user and care about the future of the code, please help out. I felt the same when I came across this during my research. I didn't have a great deal of luck in my initial efforts to reach out. It seems like Oracle/MySQL have lost a lot of interested in DBD::mysql (hence my post about this a couple of months back). Wait. That thread was about your belief that Oracle was trying to distance itself from DBD::mysql or discourage its development. Maybe I should have worded it better. The post was more to pose a question than state a belief. When I looked at the RT queue I saw the same issues that Tim has brought up now. The POD itself said to use the MySQL bug tracker and not RT, so I submitted my bug to the DBD::mysql section there. Taking into account the response I got to my patch on the MySQL bug tracker, that they removed the DBD::mysql section at the same time, the issues I found myself, the age of the last release, and the RT queue, it didn't paint a picture of this is a priority and I was given the impression that Oracle/MySQL had lost interest. I wouldn't say it's a belief, as that sounds a lot more certain. But it is the impression I get. I'm not suggesting that they want to discourage its development, just that they don't appear to view it as being as important as it once was. That would go some way to explain why it appears to have suffered from some neglect and is in need of some tlc. Which it is not. It's simply that DBD::mysql is not an Oracle product. Oracle is not responsible to fix DBD::mysql bugs. I would assume Oracle has a vested interest in it? That said, if your next statement is correct, that'd be great. However, it does appear that some activity has come back. I'm not sure if anyone looked at my patch, but I have since realised that there was a lot more amiss. DBD::mysql really needs to be updated for proper MySQL *5* support. I was talking to Peter about extra hacking sessions at our last Perl meet. I'll make sure this is on the agenda. Good, thanks. Lyle
