Fix: Use timestamp macro in sequential values test for cross-db compatibility (#376)

* pending: pending: #354

* some db's dont have `timestamp` type

* document

* Update CHANGELOG.md

Co-authored-by: Claire Carroll <20294432+clrcrl@users.noreply.github.com>
Co-authored-by: Claire Carroll <carroll.claire.e@gmail.com>

Author: dataders

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))

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 %}