|
1 | 1 | # dplyr (development version)
|
2 | 2 |
|
3 |
| -* The `rows_*()` functions now always retain the column types of `x`. This |
4 |
| - behavior was documented, but previously wasn't being applied correctly |
5 |
| - (#6240). |
6 |
| - |
| 3 | +* The `rows_*()` functions no longer require that the key values in `x` uniquely |
| 4 | + identify each row. Additionally, `rows_insert()` and `rows_delete()` no |
| 5 | + longer require that the key values in `y` uniquely identify each row. Relaxing |
| 6 | + this restriction should make these functions more practically useful for |
| 7 | + data frames, and alternative backends can enforce this in other ways as needed |
| 8 | + (i.e. through primary keys) (#5553). |
| 9 | + |
7 | 10 | * `rows_insert()` gained a new `conflict` argument allowing you greater control
|
8 | 11 | over rows in `y` with keys that conflict with keys in `x`. A conflict arises
|
9 | 12 | if a key in `y` already exists in `x`. By default, a conflict results in an
|
|
15 | 18 | argument allowing you greater control over rows in `y` with keys that are
|
16 | 19 | unmatched by the keys in `x`. By default, an unmatched key results in an
|
17 | 20 | error, but you can now also `"ignore"` these `y` rows (#5984, #5699).
|
18 |
| - |
19 |
| -* The `rows_*()` functions no longer require that the key values in `x` uniquely |
20 |
| - identify each row. Additionally, `rows_insert()` and `rows_delete()` no |
21 |
| - longer require that the key values in `y` uniquely identify each row. Relaxing |
22 |
| - this restriction should make these functions more practically useful for |
23 |
| - data frames, and alternative backends can enforce this in other ways as needed |
24 |
| - (i.e. through primary keys) (#5553). |
25 | 21 |
|
26 |
| -* The `rows_*()` functions now fail elegantly if `y` is a zero column data frame |
27 |
| - and `by` isn't specified (#6179). |
28 |
| - |
29 | 22 | * `rows_delete()` no longer requires that the columns of `y` be a strict subset
|
30 | 23 | of `x`. Only the columns specified through `by` will be utilized from `y`,
|
31 | 24 | all others will be dropped with a message.
|
32 | 25 |
|
| 26 | +* The `rows_*()` functions now always retain the column types of `x`. This |
| 27 | + behavior was documented, but previously wasn't being applied correctly |
| 28 | + (#6240). |
| 29 | + |
| 30 | +* The `rows_*()` functions now fail elegantly if `y` is a zero column data frame |
| 31 | + and `by` isn't specified (#6179). |
| 32 | + |
33 | 33 | # dplyr 1.0.8
|
34 | 34 |
|
35 | 35 | * Better display of error messages thanks to rlang 1.0.0.
|
|
0 commit comments