Restoring a dump of binary column, made with mysqldump, warns of invalid string
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
||||
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Triaged
|
Medium
|
Unassigned | |||
5.6 |
Triaged
|
Medium
|
Unassigned | |||
5.7 |
Triaged
|
Medium
|
Unassigned |
Bug Description
I am seeing a backwards-
Warning (Code 1300): Invalid utf8 character string: '9CED9D'
I believe it's related to this item in the MySQL changelog at https:/
There are a couple bugs about it such as https:/
Even if you do that, you still get the warnings when loading a mysqldump of a database that has binary data - https:/
My question is could an option be added in Percona Server to suppress this warning completely as it didn't exist in MySQL versions earlier than 5.6.27?
Or if not, could you confirm the new correct way to insert binary data into a blob is to prefix it with _binary? And if so, could mysqldump be updated to account for this?
Thanks for your help.
I don't think we will add an option to restore pre-5.6.27 behavior. The upstream considerations of how string literals are interpreted and that _binary needs to be prefixed apply to Percona Server the same. mysqldump indeed needs fixing, and let's keep this bug open for this (referring to http:// bugs.mysql. com/bug. php?id= 80150)