Fix: Use timestamp macro in sequential values test for cross-db compa…

…tibility (#376) * pending: pending: #354 * some db's dont have `timestamp` type * document * Update CHANGELOG.md Co-authored-by: Claire Carroll <[email protected]> Co-authored-by: Claire Carroll <[email protected]>
dbt-labs · Jun 1, 2021 · 00ebcb8 · 00ebcb8
1 parent 909f559
commit 00ebcb8
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,3 +1,8 @@
+# dbt-utils v0.6.6
+
+## Fixes
+
+- make `sequential_values` schema test use `dbt_utils.type_timestamp()` to allow for compatibility with db's without timestamp data type. [#376](https://github.com/fishtown-analytics/dbt-utils/pull/376) from [@swanderz](https://github.com/swanderz)
 # dbt-utils v0.6.5
 ## Features
 * Add new `accepted_range` test ([#276](https://github.com/fishtown-analytics/dbt-utils/pull/276) [@joellabes](https://github.com/joellabes))

diff --git a/macros/schema_tests/sequential_values.sql b/macros/schema_tests/sequential_values.sql
@@ -21,7 +21,7 @@ validation_errors as (
         *
     from windowed
     {% if datepart %}
-    where not(cast({{ column_name }} as timestamp)= cast({{ dbt_utils.dateadd(datepart, interval, 'previous_' + column_name) }} as timestamp))
+    where not(cast({{ column_name }} as {{ dbt_utils.type_timestamp() }})= cast({{ dbt_utils.dateadd(datepart, interval, 'previous_' + column_name) }} as {{ dbt_utils.type_timestamp() }}))
     {% else %}
     where not({{ column_name }} = previous_{{ column_name }} + {{ interval }})
     {% endif %}