On 09/13/2017 09:58 PM, Dan Book wrote:
On Wed, Sep 13, 2017 at 3:53 AM, Peter Rabbitson <rab...@rabbit.us
<mailto:rab...@rabbit.us>> wrote:
On 09/12/2017 07:12 PM, p...@cpan.org <mailto:p...@cpan.org> wrote:
On Tuesday 12 September 2017 12:27:25 p...@cpan.org
<mailto: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 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.
If you were to actually try to make the requested addition you'd have
noticed that DBD::Pg *DOES NOT* require one to binding with SQL_BLOB.
For more info please go back to the old ( 2013 ) RT threads on the
"mysql unicode issue" and read again carefully.
Please try to actually implement this - it will give you additional
perspective.
