Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Snapshot updates for rcc-full ({"config":{"os":"ubuntu-22.04","r":"release","test-src":"test-duckdb","covr":true,"desc":"DuckDB with covr"}}) #2170

Closed
wants to merge 1 commit into from
Closed

Snapshot updates for rcc-full ({"config":{"os":"ubuntu-22.04","r":"release","test-src":"test-duckdb","covr":true,"desc":"DuckDB with covr"}}) #2170

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions tests/testthat/_snaps/filter-dm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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
Expand All @@ -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
Expand All @@ -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
Expand All @@ -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
Expand All @@ -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
Expand Down Expand Up @@ -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
Expand Down