[create-pull-request] automated change

Author: aviator-app[bot]

tests/testthat/_snaps/filter-dm.md

@@ -7,6 +7,8 @@
       The `table` argument of `dm_filter()` is deprecated as of dm 1.0.0.
       i `dm_filter()` now takes named filter expressions, the names correspond to the tables to be filtered. You no longer need to call `dm_apply_filters()` to materialize the filters.
     Output
+      -- Table source ----------------------------------------------------------------
+      src:  DuckDB v0.9.2 [unknown@Linux 6.2.0-1018-azure:R 4.3.2/:memory:]
       -- Metadata --------------------------------------------------------------------
       Tables: `tf_1`, `tf_2`, `tf_3`, `tf_4`, `tf_5`, `tf_6`
       Columns: 20
@@ -24,6 +26,8 @@
       The `table` argument of `dm_filter()` is deprecated as of dm 1.0.0.
       i `dm_filter()` now takes named filter expressions, the names correspond to the tables to be filtered. You no longer need to call `dm_apply_filters()` to materialize the filters.
     Output
+      -- Table source ----------------------------------------------------------------
+      src:  DuckDB v0.9.2 [unknown@Linux 6.2.0-1018-azure:R 4.3.2/:memory:]
       -- Metadata --------------------------------------------------------------------
       Tables: `tf_1`, `tf_2`, `tf_3`, `tf_4`, `tf_5`, `tf_6`
       Columns: 20
@@ -38,6 +42,8 @@
       The `table` argument of `dm_filter()` is deprecated as of dm 1.0.0.
       i `dm_filter()` now takes named filter expressions, the names correspond to the tables to be filtered. You no longer need to call `dm_apply_filters()` to materialize the filters.
     Output
+      -- Table source ----------------------------------------------------------------
+      src:  DuckDB v0.9.2 [unknown@Linux 6.2.0-1018-azure:R 4.3.2/:memory:]
       -- Metadata --------------------------------------------------------------------
       Tables: `tf_1`, `tf_2`, `tf_3`, `tf_4`, `tf_5`, `tf_6`
       Columns: 20
@@ -50,6 +56,8 @@
       `dm_apply_filters()` was deprecated in dm 1.0.0.
       i Calling `dm_apply_filters()` after `dm_filter()` is no longer necessary.
     Output
+      -- Table source ----------------------------------------------------------------
+      src:  DuckDB v0.9.2 [unknown@Linux 6.2.0-1018-azure:R 4.3.2/:memory:]
       -- Metadata --------------------------------------------------------------------
       Tables: `tf_1`, `tf_2`, `tf_3`, `tf_4`, `tf_5`, `tf_6`
       Columns: 20
@@ -62,7 +70,6 @@
       The `table` argument of `dm_filter()` is deprecated as of dm 1.0.0.
       i `dm_filter()` now takes named filter expressions, the names correspond to the tables to be filtered. You no longer need to call `dm_apply_filters()` to materialize the filters.
     Output
-      # A tibble: 3 x 4
         c         d e        e1
         <chr> <int> <chr> <int>
       1 worm      5 G         7
@@ -75,7 +82,6 @@
       `dm_apply_filters_to_tbl()` was deprecated in dm 1.0.0.
       i Access tables directly after `dm_filter()`.
     Output
-      # A tibble: 3 x 4
         c         d e        e1
         <chr> <int> <chr> <int>
       1 worm      5 G         7
@@ -223,6 +229,9 @@
     Code
       dm_for_filter_rev() %>% dm_filter(tf_1 = a < 8 & a > 3) %>% dm_get_tables() %>%
         map(harmonize_tbl)
+    Condition
+      Warning:
+      Autoincrementing columns not yet supported for DuckDB, these won't be set in the remote database but are preserved in the `dm`
     Output
       $tf_6
       # A tibble: 2 x 3