Re: DBD::mysql path forward
Dan Book <[email protected]>
| Newsgroups | gmane.comp.lang.perl.modules.dbi.sybase.devel,gmane.comp.lang.perl.modules.dbi.general |
|---|---|
| Message-ID | <CABMkAVW9icJVo2MZRe=yH0d3=SJZDxJF1LnW3BiRY6zLbQRW9A@mail.gmail.com> |
On Wed, Sep 13, 2017 at 3:53 AM, Peter Rabbitson <[email protected]> wrote: > On 09/12/2017 07:12 PM, [email protected] wrote: > >> On Tuesday 12 September 2017 12:27:25 [email protected] 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 between Pg, >>> SQLite and mysql DBI drivers. >>> >> >> And here is promised script: >> >> > <snip> > > The script side-steps showcasing the treatment of BLOB/BYTEA columns, > which was one of the main ( albeit not the only ) reason the userbase lost > data. > > Please extend the script with a BLOB/BYTEA test. > I'm not sure how to usefully make such a script, since correct insertion of BLOB data (binding with the SQL_BLOB type or similar) would work correctly both before and after the fix. -Dan