-
Notifications
You must be signed in to change notification settings - Fork 24
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
psycopg2.IntegrityError: null value in column "uid" violates not-null constraint #7
Comments
try it with PR #9 . Interesting that we find the same issues independently :) |
I confirmed this fixes the issue, thanks! |
I'm running into this same issue. Any chance this could be merged in? |
@robmoore try this, maybe it will for you https://github.com/datamill-co/target-redshift |
That project doesn't support STATE which is a no-go for us. No way we could possibly do full table reloads. @robmoore I made a fork with this and #6 that seems to be working well for us pip install git+https://github.com/djdevin/target-postgres.git |
@djdevin You might want to take a look at the 'other' version of target-postgres: https://github.com/datamill-co/target-postgres I've been using it and found it handles things like null values better. Also, it seems to be more actively developed. |
Strange issue where an integer 0 is being converted to a NULL and breaking the copy as the resulting table does not allow nulls.
The row in question here has an int(11) 0 in the
uid
column.If I just delete the row with the 0, it will copy fine.
Coming from
tap-mysql
it looks like it is providing the correct value for the row:The text was updated successfully, but these errors were encountered: