New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
lifeboy opened this Issue Oct 15, 2017 · 0 comments

Comments

Projects
2 participants
@lifeboy

lifeboy commented Oct 15, 2017

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment