Bugfix/timestamp casts

[fivetran-joemarkiewicz]

Are you a current Fivetran customer?

Fivetran created PR

What change(s) does this PR introduce?

A customer identified that date functions in the dbt_github dbt package fail for Redshift users as the timestamp fields are being synced as timestamptz instead of timestamp. This is a similar issue we have seen in other packages and the route to resolve the issue is to cast the fields within the source package to reflect the more accurate timestamp field for Redshift users. For cross dbt functionality we will use the dbt_util.

Does this PR introduce a breaking change?

• Yes (please provide breaking change details below.)
• No (please provide explanation how the change is non breaking below.)

This update will be an under the hood change where we simply cast the timestamp fields as a dbt_utils.timestamp() in order to account for Fivetran Redshift users experiencing the timestamp fields being synced as timestamptz and failing during date functions in downstream transformations.

Is this PR in response to a previously created Issue

• Yes, Issue #25
• No

How did you test the PR changes?

• CircleCi
• Other (please provide additional testing details below)

Select which warehouse(s) were used to test the PR

• BigQuery
• Redshift
• Snowflake
• Postgres
• Databricks
• Other (provide details below)

Provide an emoji that best describes your current mood

⌚

Feedback

We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.

[fivetran-sheringuyen]

lgtm!