Re: Fork DBD::mysql

2017-09-01 Thread Patrick M. Galbraith
Hi Pali, I would very much like to address these issues and fix the UTF issue you so kindly had a patch for that people had problems with and do so in a way that doesn't require forking. I'm very sorry about this as I was in between jobs and distracted but am free next week to discuss this. I

Re: Fork DBD::mysql

2017-09-01 Thread pali
On Friday 01 September 2017 13:36:13 H.Merijn Brand wrote: > On Fri, 1 Sep 2017 13:08:17 +0200, p...@cpan.org wrote: > > > On Tuesday 29 August 2017 22:08:09 Dan Book wrote: > > > Though the reversion was made with good intentions of preserving back > > > compat in the short term, it was

Re: Fork DBD::mysql

2017-09-01 Thread H.Merijn Brand
On Fri, 1 Sep 2017 13:08:17 +0200, p...@cpan.org wrote: > On Tuesday 29 August 2017 22:08:09 Dan Book wrote: > > Though the reversion was made with good intentions of preserving back > > compat in the short term, it was accompanied by a promise of reapplying the > > many important fixes that were

Re: Fork DBD::mysql

2017-09-01 Thread pali
On Tuesday 29 August 2017 22:08:09 Dan Book wrote: > Though the reversion was made with good intentions of preserving back > compat in the short term, it was accompanied by a promise of reapplying the > many important fixes that were reverted ( >

Re: [External] Fork DBD::mysql

2017-08-29 Thread Dan Book
On Tue, Aug 29, 2017 at 3:36 AM, wrote: > Then users of MySQL would stay with DBD::mysql and they would not have > fixed DBD driver. We were thinking about choosing DBD::mariadb name > for our fork. But without dropping MySQL support, so also MySQL users > could benefit from it. >

Re: Fork DBD::mysql

2017-08-29 Thread pali
On Monday 28 August 2017 09:19:46 Darren Duncan wrote: > While a fork may be the best short term fix, as keeping up with security > issues is important, I honestly believe that the best fix is to migrate to > Postgres as soon as you can. It is not as easy as it could appear. And also in some

Re: [External] Fork DBD::mysql

2017-08-29 Thread pali
Then users of MySQL would stay with DBD::mysql and they would not have fixed DBD driver. We were thinking about choosing DBD::mariadb name for our fork. But without dropping MySQL support, so also MySQL users could benefit from it. On Monday 28 August 2017 18:08:20 Daniël van Eeden wrote: > What

Re: Fork DBD::mysql

2017-08-28 Thread Alexander Foken
On 28.08.2017 18:19, Darren Duncan wrote: On 2017-08-28 8:55 AM, p...@cpan.org wrote: Because of the current situation we in the GoodData company are thinking about forking DBD::mysql. We use DBI not only with DBD::mysql, but also with DBD::Pg. The annoying bugs in DBD::mysql still require

Re: Fork DBD::mysql

2017-08-28 Thread Darren Duncan
On 2017-08-28 12:00 PM, Alexander Foken wrote: On 28.08.2017 18:19, Darren Duncan wrote: While a fork may be the best short term fix, as keeping up with security issues is important, ... Not being able to connect to MySQL / MariaDB from Perl is not acceptable. Having tons of known bugs,

Re: Fork DBD::mysql

2017-08-28 Thread David Nicol
It looks like this fork happened some time ago, and a DBD::maria is now needed, to keep up. Is that not what it looks like? -- everything has to be just so or the magic won't work

Re: Fork DBD::mysql

2017-08-28 Thread Darren Duncan
On 2017-08-28 8:55 AM, p...@cpan.org wrote: Because of the current situation we in the GoodData company are thinking about forking DBD::mysql. We use DBI not only with DBD::mysql, but also with DBD::Pg. The annoying bugs in DBD::mysql still require hacks and workarounds, while similar bugs were

Fork DBD::mysql

2017-08-28 Thread pali
Hello, 2 months passed since two security problems related to DBD::mysql were reported, namely CVE-2017-10789 and CVE-2017-10788. Looking at the DBD::mysql github project page and RT bugtracker, it can be seen that nothing has happened for 2 months. Some people are asking or waiting for reported