-
Notifications
You must be signed in to change notification settings - Fork 21
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
feat: Configurable null character sanitization #434
Conversation
011036c
to
330501b
Compare
Good evening 👋 I’ve been trying to sync an MSSQL database and ran into the same issue with null values causing failures and this PR seems to have resolved the problem for me. I am not an active contributor to the project yet but let me know if there’s anything I can do to help get this merged—happy to assist! |
Hi @nickjoanis! The first thing would be addressing the merge conflicts |
Null characters are currently passed as-is to Postgres despite being unsupported.
If it is encountered, it causes the sink to fail as noted here: #60 with an error like
ValueError: A string literal cannot contain NUL (0x00) characters.
This PR introduces a new option called
sanitize_null_text_characters
which enables sanitization of these characters.