Join GitHub today
pg can't handle NUL characters in string, but MySQL/MariaDB can. Migration of rows fails. #33
When debug log level is on, the following is found:
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?