Re: DBD::mysql path forward

Dan Book <[email protected]> Tue, 12 Sep 2017 12:09:13 -0400

Newsgroups	gmane.comp.lang.perl.modules.dbi.general,gmane.comp.lang.perl.modules.dbi.sybase.devel
Message-ID	<CABMkAVXPfAETFd39SL+9y7KXLDcNikiyJ4_qx-6iS7MnRpXX+Q@mail.gmail.com>

On Tue, Sep 12, 2017 at 11:54 AM, Dan Book <[email protected]> wrote:

> On Tue, Sep 12, 2017 at 11:04 AM, Patrick M. Galbraith <[email protected]>
> wrote:
>
>> Pali,
>>
>> Yes, I agree, we'll have to create a fork pre revert and stop accepting
>> PRs
>>
>> How might we allow people time to test the fixes to give them time? Just
>> have them use the fork, I would assume?
>>
>> Regards,
>>
>> Patrick
>>
>
> To be clear, this sounds like a branch not a fork. If your plan is to
> reinstate the mysql_enable_utf8 behavior as in 4.042 rather than adding a
> new option for this behavior, then branching from 4.042 seems reasonable to
> me; but you should be very clear if this is your intended approach, as this
> is what led to many people corrupting data as they send blobs to mysql with
> the same mysql_enable_utf8 option, and expect them to accidentally not get
> encoded.
>
> -Dan
>

And one other note, if you do reinstate the 4.042 behavior, due to the
backcompat breakage at the very least this should be a 5.0 release.

-Dan