Tags: erictleung/dm
Tags
dm 0.2.3.9004 # dm 0.2.3.9004 - Establish compatibility with vctrs > 0.3.8. - Establish compatibility with rlang > 0.4.11 (cynkra#613).
dm 0.2.3.9003 # dm 0.2.3.9003 - `rows_insert()`, `rows_update()` and `rows_delete()` gain `returning` argument. In combination with `in_place = TRUE` this argument makes the newly inserted rows accessible via `get_returning_rows()` after the operation completes (cynkra#593, @mgirlich).
dm 0.2.3.9002 # dm 0.2.3.9002 - Update tests for pillar 1.6.2. - Add CI run for validating all new `dm` objects (cynkra#597). - Avoid generating invalid `dm` objects in some corner cases (cynkra#596).
dm 0.2.3.9001 # dm 0.2.3.9001 - Use `NO ACTION` instead of `CASCADE` in foreign key constraints to permit self-references.
dm 0.2.3 # dm 0.2.3 ## Bug fixes - Fix `rows_truncate()` in interactive mode (cynkra#588). ## Features - Implement `rows_delete()` for databases (cynkra#589). ## Internal - Skip examples that might require internet access on non-CI platforms.
dm 0.2.3.9000 # dm 0.2.3.9000 - Same as previous version.
dm 0.2.2.9001 # dm 0.2.2.9001 - Implement `rows_delete()` for databases (cynkra#589). - Fix `rows_truncate()` in interactive mode (cynkra#588).
dm 0.2.2 # dm 0.2.2 ## Features - `dm_examine_constraints()`, `dm_rows_insert()` and related, `copy_dm_to()` and `collect.dm()` show progress bars in interactive mode via the progress package. The new `progress = NA` argument controls the behavior (cynkra#262, @moodymudskipper). - `copy_dm_to()` gains a `copy_to` argument to support other ways of copying data to the database (cynkra#582). ## Internal - Always run database tests on sqlite for df source. - Establish compatibility with testthat > 3.0.2 (cynkra#566, @moodymudskipper).
dm 0.2.2.9000 # dm 0.2.2.9000 - Same as previous version.
dm 0.2.1.9002 # dm 0.2.1.9002 - Always run database tests on sqlite for df source. - `collect.dm()` gains `progress` argument (cynkra#582). - `copy_dm_to()` gains `progress` and `copy_to` arguments (cynkra#582).
PreviousNext