dave-connors-3

@b-per updated the logic to handle nulls a bit more gracefully -- local integration tests are running fine for databricks (both folders). Can't seem to replicate the error from Circle...

@graciegoheen this change should avoid the need to pass those overrides at all -- this will ensure that the null is properly cast as strings before we attempt to union...

> You mentioned that you don't want to add 30 tests to check if strings are not empty, which is fair. Can we add at least one or two tests...

This came up again in #221 ! flagging this as a good issue to priortize once we an agree on a strategy here

Agree with @b-per here -- this is definitely a pattern I have seen (and used!) for when there are identical data sources across schemas -- union from the sources directly,...

utils should have [some](https://github.com/dbt-labs/dbt-utils/tree/main/tests), but these may just be ported over from core as they migrated the cross db utils. [Metrics also has pytest based testing](https://github.com/dbt-labs/dbt_metrics/tree/main/tests)

hey @qmoret -- can you give a bit more detail into the model code you have in this staging model? Curious to see how the `star` macro ends up with...

hey @jtcohen6! I think we should be good to go on added tests -- [Spark](https://github.com/dbt-labs/dbt-spark/pull/390) [BQ](https://github.com/dbt-labs/dbt-bigquery/pull/227) [Snowflake](https://github.com/dbt-labs/dbt-snowflake/pull/206) I likely missed something, so let me know what else needs to be...

whoa who knew! Definitely open to changing it! I have never chained flags together as i'm sure you can tell

Despite my love for the very memeable `-fr`, I am convinced