You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: