You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rows_update() to allow key to be a pipdaExpression
rows_update(), rows_patch(), and rows_delete() gained a new unmatched
argument allowing you greater control over rows in y with keys that are
unmatched by the keys in x. By default, an unmatched key results in an
error, but you can now also "ignore" these y rows.
rows_delete() no longer requires that the columns of y be a strict subset
of x. Only the columns specified through by will be utilized from y,
all others will be dropped with a message.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Feature Type
Adding new functionality to datar
Changing existing functionality in datar
Removing existing functionality in datar
Problem Description
https://github.com/tidyverse/dplyr/releases/tag/v1.0.9
Feature Description
rows_update()
to allowkey
to be not uniquerows_update()
to allowkey
to be apipda
Expression
rows_update()
,rows_patch()
, androws_delete()
gained a new unmatchedargument allowing you greater control over rows in y with keys that are
unmatched by the keys in x. By default, an unmatched key results in an
error, but you can now also "ignore" these y rows.
rows_delete()
no longer requires that the columns of y be a strict subsetof x. Only the columns specified through by will be utilized from y,
all others will be dropped with a message.
Additional Context
No response
The text was updated successfully, but these errors were encountered: