Describe the bug
When running WhiteRabbit against a Snowflake instance with multiple databases and/or schema's, tables are not always properly identified by the correct database & schema, leading to crashes and/or errors reporting non-existent tables or columns.
To Reproduce
Steps to reproduce the behavior:
This requires a Snowflake instance with multiple database and/or schema's and duplicate column names across tables
to reproduce. Bug fixes will need to be field-tested with instances that have these features.
Expected behavior
Snowflake tables and columns should always be identified by the correct database and schema.
Desktop (please complete the following information):
- OS: any
- Version v1.0.0-RC1
Additional context
Add any other context about the problem here.
Describe the bug
When running WhiteRabbit against a Snowflake instance with multiple databases and/or schema's, tables are not always properly identified by the correct database & schema, leading to crashes and/or errors reporting non-existent tables or columns.
To Reproduce
Steps to reproduce the behavior:
This requires a Snowflake instance with multiple database and/or schema's and duplicate column names across tables
to reproduce. Bug fixes will need to be field-tested with instances that have these features.
Expected behavior
Snowflake tables and columns should always be identified by the correct database and schema.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.