Add any value (#501)

* Add link for fewer_rows_than schema test in docs (#465)

* Update get_query_results_as_dict example to demonstrate accessing columnar results as dictionary values (#474)

* Update get_qu
ery_results_as_dict example to demonstrate accessing columnar results as dictionary values

* Use slugify in example

* Fix slugify example with dbt_utils. package prefix

Co-authored-by: Elize Papineau <[email protected]>

* Add note about not_null_where deprecation to Readme (#477)

* Add note about not_null_where deprecation to Readme

* Add docs to unique_where test

* Update pull_request_template.md to reference `main` vs `master` (#496)

* Correct coalesce -> concatenation typo (#495)

* add any_value cross-db macro

* Missing colon in test

* Update CHANGELOG.md

Co-authored-by: José Coto <[email protected]>
Co-authored-by: Elize Papineau <[email protected]>
Co-authored-by: Elize Papineau <[email protected]>
Co-authored-by: Joe Ste.Marie <[email protected]>
Co-authored-by: Niall Woodward <[email protected]>

CHANGELOG.md

@@ -1,5 +1,8 @@
 # dbt-utils v0.8.1
 
+## New features
+- A cross-database implementation of `any_value()` ([#497](https://github.com/dbt-labs/dbt-utils/issues/497), [#501](https://github.com/dbt-labs/dbt-utils/pull/501))
+
 ## Under the hood
 - also ignore `dbt_packages/` directory [#463](https://github.com/dbt-labs/dbt-utils/pull/463)
 

README.md

@@ -461,7 +461,7 @@ in isolation.
 We generally recommend testing this uniqueness condition by either:
 * generating a [surrogate_key](#surrogate_key-source) for your model and testing
 the uniqueness of said key, OR
-* passing the `unique` test a coalesce of the columns (as discussed [here](https://docs.getdbt.com/docs/building-a-dbt-project/testing-and-documentation/testing/#testing-expressions)).
+* passing the `unique` test a concatenation of the columns (as discussed [here](https://docs.getdbt.com/docs/building-a-dbt-project/testing-and-documentation/testing/#testing-expressions)).
 
 However, these approaches can become non-perfomant on large data sets, in which
 case we recommend using this test instead.

integration_tests/data/cross_db/data_any_value_expected.csv

@@ -0,0 +1,4 @@
+key_name,static_col,num_rows
+abc,dbt,2
+jkl,dbt,3
+xyz,test,1

integration_tests/models/cross_db_utils/schema.yml

@@ -1,6 +1,12 @@
 version: 2
 
 models:
+  - name: test_any_value
+    tests:
+      - dbt_utils.equality:
+          compare_model: ref('data_any_value_expected')
+
+
   - name: test_concat
     tests:
       - assert_equal:

integration_tests/models/cross_db_utils/test_any_value.sql

@@ -0,0 +1,19 @@
+with some_model as (
+    select 1 as id, 'abc' as key_name, 'dbt' as static_col union all 
+    select 2 as id, 'abc' as key_name, 'dbt' as static_col union all
+    select 3 as id, 'jkl' as key_name, 'dbt' as static_col union all
+    select 4 as id, 'jkl' as key_name, 'dbt' as static_col union all
+    select 5 as id, 'jkl' as key_name, 'dbt' as static_col union all
+    select 6 as id, 'xyz' as key_name, 'test' as static_col
+),
+
+final as (
+    select 
+        key_name, 
+        {{ dbt_utils.any_value('static_col') }} as static_col, 
+        count(id) as num_rows
+    from some_model
+    group by key_name
+)
+
+select * from final

macros/cross_db_utils/any_value.sql

@@ -0,0 +1,17 @@
+{% macro any_value(expression) -%}
+    {{ return(adapter.dispatch('any_value', 'dbt_utils') (expression)) }}
+{% endmacro %}
+
+
+{% macro default__any_value(expression) -%}
+
+    any_value({{ expression }})
+
+{%- endmacro %}
+
+
+{% macro postgres__any_value(expression) -%}
+    {#- /*Postgres doesn't support any_value, so we're using min() to get the same result*/ -#}
+    min({{ expression }})
+
+{%- endmacro %}