On 26 September 2017 at 12:15, Night Light wrote:
> The corruption is caused by the fact that the data type of a BLOB can not be
> recognized and is therefore UTF8 encoded like a string before being sent to
> MySQL.
Which means it can be fixed. And in a sane scenario will be detectable.
Corrupti
That's a nifty function. Good to know that it can be reversed.
I noticed that it was mentioned in DBD::mysql # 117 that DBD::mysql does
know that a column in a returned resultset is a BLOB.
One should also consider the performance penalty of encoding/decoding
BLOB's as they can be big.
On Tue, Sep
On 19 September 2017 at 14:46, Night Light wrote:
> Dear Perl gurus,
>
> This is my first post. I'm using Perl with great joy, and I'd like to
> express my gratitude for all you are doing to keep Perl stable and fun to
> use.
>
> I'd like to ask to object to re-releasing this version and discuss o
The corruption is caused by the fact that the data type of a BLOB can not
be recognized and is therefore UTF8 encoded like a string before being sent
to MySQL.
I'd like to propose the introduction of an attribute to ensure correct UTF8
encoding while maintaining backwards compatibility.
Manual page
