DESCRIBE EXTENDED truncates column types. For generating doc site, this is ok, but for running a dbt project, it can cause issues. Where information_schema is available, we can use it to get an un-truncated column type. Initially I was going to hide this behind a behavior flag, since both methods can have performance issues; however, during implementation I discovered that behavior flags aren't available to adapters yet, due to the current dbt-core not having flags on the RuntimeConfig object. So, plan is to use information_schema where available, as it is more correct. Once behavior flags are available, we can allow users to choose, so that if one way is less performant, they can switch.
Checklist
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have updated the CHANGELOG.md and added information about my change to the "dbt-databricks next" section.
Resolves #779 (for UC)
Description
DESCRIBE EXTENDEDtruncates column types. For generating doc site, this is ok, but for running a dbt project, it can cause issues. Where information_schema is available, we can use it to get an un-truncated column type. Initially I was going to hide this behind a behavior flag, since both methods can have performance issues; however, during implementation I discovered that behavior flags aren't available to adapters yet, due to the current dbt-core not having flags on the RuntimeConfig object. So, plan is to use information_schema where available, as it is more correct. Once behavior flags are available, we can allow users to choose, so that if one way is less performant, they can switch.Checklist
CHANGELOG.mdand added information about my change to the "dbt-databricks next" section.