Added case_sensitive_cols argument to generate_base_model macro

[graciegoheen]

This is a:

• bug fix PR with no breaking changes — please ensure the base branch is main
• new functionality — please ensure the base branch is the latest dev/ branch
• a breaking change — please ensure the base branch is the latest dev/ branch

Description & motivation

I added an argument case_sensitive_cols to generate_base_model macro to allow this macro to still work for source tables with case sensitive column names.

Checklist

• I have verified that these changes work locally (Snowflake)
• I have updated the README.md (if applicable)
• I have added tests & descriptions to my models (and macros if applicable)
• I have added an entry to CHANGELOG.md

[b-per]

LGTM!
Just a quick comment about describing what the new parameter actually does

[b-per]

Oh, and I didn't see that it fails for Redshift. Not sure why this is the case though.

[graciegoheen]

I'm guessing it's this - https://docs.aws.amazon.com/redshift/latest/dg/r_enable_case_sensitive_identifier.html

[graciegoheen]

Column names in Google BigQuery are not able to be case sensitive... I updated the logic to remove the "" wrapping that was throwing an error for BigQuery only. So the generate_base_model macro will still use the CaseSensitive source column names but won't be quoted. Example in BigQuery:

...
    select
        My_Integer_Col,
        My_Bool_Col

    from source
...

Example in other data warehouse:

...
    select
        "My_Integer_Col",
        "My_Bool_Col"

    from source
...

[dbeatty10]

It would be awesome if there's some property of the adapter itself that we can use for handling columns that should/shouldn't be quoted. That would enable us to just apply whatever that logic is rather than requiring logic like if target.type == "bigquery".

Here's some examples of the kind of thing I'm thinking of:

• https://docs.getdbt.com/reference/resource-properties/quote
• https://docs.getdbt.com/reference/project-configs/quoting
• https://docs.getdbt.com/reference/resource-configs/quote_columns

Since this is working and for sake of expediency, I didn't research if any of these (or alternatives) would be applicable to this case though.

We can circle back later and attempt to generalize it if we so need or desire.