Re: DBD::mysql path forward

On 2017-11-09 12:54 AM, [email protected] wrote:
> On Tuesday 07 November 2017 13:19:23 Darren Duncan wrote:
>> The whole discussion on the mailing lists that I recall and participated in
>> seemed to consensus on branching DBD::sqlite in order to best satisfy the
>                                    ~~~~~~~~~~
>                                    DBD::mysql
>
> I hope you are talking about DBD::mysql there...

Yes, that was a typo, I was talking exclusively about DBD::mysql here.

That being said, as an aside, DBD::SQLite (and yes I meant that) is still a 
valuable case study in that they also branched, back 14 years ago when SQLite 3 
came out, using in that case DBD::SQLite2 that bundled the SQLite version 2 and 
repurposing DBD::SQLite name, and bumping from version 0.33 to 1.0, to now 
bundle the incompatible SQLite 3.  In their case, it was a break for people that 
simply upgraded the usual CPAN manner, and the fork was for people that still 
needed to use SQLite 2 in Perl.  DBD::mysql doesn't want to follow their example.

-- Darren Duncan