'SNOWFLAKE : Constraint on table that doesn't exists
I use INFORMATON_SCHEMA.TABLE_CONSTRAINTS in a stored procedure to dynamically generate a uniqueness check on the tables. It works fine until I have a constraint that refers to a table that does not exist or no longer exists.
Have you ever been confronted with this situation? Is there a way to clean the information_schema
thanks
Solution 1:[1]
Join to SNOWFLAKE.ACCOUNT_USAGE.TABLES, you'll find column DELETED there, use it for filtering.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | Limonka |