Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Not a Bug
-
1.1.7
-
None
-
None
-
Windows 7, 64bit
Description
I posted a description of this bug here:
Additional Infos:
I feel this is a bug and not a feature because the insert works perfectly.
If I use the UF8 character "C2 92" ([-62, -110]) instead of the japanese character, I get the same error AND the posted workaround does not work.
Originally, this problem comes from a data replication between oracle (source) and mariaDB (destination), where it is possible that I get characters which are not assigned in latin1.