Skip to content
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

Snowflake behaviour change - enforce not null primary key column #735

Open
EamonKeane opened this issue Jul 2, 2021 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@EamonKeane
Copy link

Snowflake have today corrected a bug whereby primary key columns which were not previously enforced to be not null, now are.

In mysql-snowflake fast-sync an empty string is treated as null. In my case I have a multi-column primary key one of whose columns is an empty string. With the new behaviour change, this now errors out with a not null.

The solution in this case would be I guess to represent an empty string as '' in the csv which would get around the error.

https://community.snowflake.com/s/article/Change-to-Enforcement-of-PRIMARY-KEYS-created-by-CREATE-TABLE-Commands-Pending

@EamonKeane EamonKeane added the enhancement New feature or request label Jul 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant