Re: DBD::mysql path forward

2017-09-13 Thread Darren Duncan
On 2017-09-13 12:58 PM, Dan Book wrote: On Wed, Sep 13, 2017 at 3:53 AM, Peter Rabbitson wrote: On 09/12/2017 07:12 PM, p...@cpan.org wrote: And here is promised script: The script side-steps showcasing the treatment of BLOB/BYTEA columns, which was one of the main (

Re: DBD::mysql path forward

2017-09-13 Thread Peter Rabbitson
On 09/13/2017 09:58 PM, Dan Book wrote: On Wed, Sep 13, 2017 at 3:53 AM, Peter Rabbitson > wrote: On 09/12/2017 07:12 PM, p...@cpan.org wrote: On Tuesday 12 September 2017 12:27:25 p...@cpan.org

Re: DBD::mysql path forward

2017-09-13 Thread Dan Book
On Wed, Sep 13, 2017 at 3:53 AM, Peter Rabbitson wrote: > On 09/12/2017 07:12 PM, p...@cpan.org wrote: > >> On Tuesday 12 September 2017 12:27:25 p...@cpan.org wrote: >> >>> To prove fact that other DBI drivers (e.g. Pg or SQLite) had fixed >>> similar/same UTF-8 issue as MySQL

Re: DBD::mysql path forward

2017-09-13 Thread Darren Duncan
On 2017-09-13 6:31 AM, p...@cpan.org wrote: On Tuesday 12 September 2017 11:32:36 Darren Duncan wrote: Regardless, following point 2, mandate that all Git pull requests are made against the new 5.x master; the 4.x legacy branch would have no commits except minimal back-porting. New pull

Re: DBD::mysql path forward

2017-09-13 Thread pali
On Tuesday 12 September 2017 11:32:36 Darren Duncan wrote: > On 2017-09-12 11:05 AM, p...@cpan.org wrote: > >On Tuesday 12 September 2017 19:00:59 Darren Duncan wrote: > >>I strongly recommend that another thing happen, which is > >>re-versioning DBD::mysql to 5.0. > >> > >>1. From now on,

Re: DBD::mysql path forward

2017-09-13 Thread Peter Rabbitson
On 09/12/2017 07:12 PM, p...@cpan.org wrote: On Tuesday 12 September 2017 12:27:25 p...@cpan.org wrote: To prove fact that other DBI drivers (e.g. Pg or SQLite) had fixed similar/same UTF-8 issue as MySQL has and behave Perl-correctly, I would provide test cases so you would see difference

Re: DBD::mysql path forward

2017-09-13 Thread pali
I would suggest to communicate with all people behind cpan modules which uses mysql_enable_utf8. https://grep.metacpan.org/search?size=20=mysql_enable_utf8== They should know if their modules are expecting old broken or behavior of DBD::mysql or not. I would expect that are modules which needs