pg can't handle NUL characters in string, but MySQL/MariaDB can. Migration of rows fails.

[lifeboy]

When debug log level is on, the following is found:

[ERROR] - pg_lib.py (547): unexpected error when processing the row
[ERROR] - pg_lib.py (548):  - > Table: deposit_imports
[ERROR] - pg_lib.py (549):  - > Insert list: "id","deposit_date","source","record_amount","reference","code"
[ERROR] - pg_lib.py (550):  - > Insert values: ['219456', '020160624', 'H2H', '+0000000005000.00',  '             \x00\x0001234567890     '

This can be addressed by replacing the NUL's in MySQL with a space, but it means the original data is changed, which we want to avoid.

Can a method be incorporated to check for NUL's in MySQL data strings on replication, since this is essentially an integral part of a migration process, especially if it is not a once off exercise?